> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vulpy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Take your Vulpy Commerce shop live

> Add a live environment, point DNS, verify Matomo, and cut over from a noindex preview host to your apex domain with pnpm vulpy env golive.

Vulpy Commerce ships dev plus Fox on a fresh install. Adding live is a separate, deliberate step that only a human on the server can run. This page walks through the golive flow, the DNS records you need, and the Matomo gate.

<Tip>
  **Ask Fox for the plan; you press the button.** `env golive live` refuses inside Fox by design, but Fox drafts the whole sequence and audits it with you first.

  Try prompts like:

  * "Explain the golive flow step by step."
  * "Draft a pre-golive checklist."
  * "Why would `env golive live` refuse?"
</Tip>

## Steps

<Steps>
  <Step title="Add the live environment">
    Run this on the VPS as the deploy user (`sudo -iu vulpy-commerce`):

    ```bash theme={null}
    pnpm vulpy env add live
    ```

    The command adds domains, builds and starts services, and runs Matomo setup as part of the flow.
  </Step>

  <Step title="Point DNS">
    Create records for the four live hostnames. Defaults are labels; you can override them via install flags.

    | Record           | Points to                   | Notes                                  |
    | ---------------- | --------------------------- | -------------------------------------- |
    | `SHOP_DOMAIN`    | Storefront apex             | `www.` 301s here                       |
    | `PREVIEW_DOMAIN` | Preview shop                | Noindex until golive; then 301 to apex |
    | `API_DOMAIN`     | Medusa API and `/app` admin |                                        |
    | `MATOMO_DOMAIN`  | Self-hosted Matomo          | Default `analytics.<domain>`           |
  </Step>

  <Step title="Verify Matomo">
    Run the privacy and legal gate check. Golive refuses without it.

    ```bash theme={null}
    pnpm deploy:matomo:verify
    ```
  </Step>

  <Step title="Cut over">
    Promote preview to apex:

    ```bash theme={null}
    pnpm vulpy env golive live
    ```

    On success, the preview host 301s to the apex and the shop is public.
  </Step>
</Steps>

<Warning>
  `pnpm vulpy env golive live` refuses without a baked Matomo site id and a running Matomo container. Self-hosting is not a consent exemption, so plan for consent UX on the storefront too.
</Warning>

<Tip>
  **B2B price gating:** set `REQUIRE_LOGIN_FOR_PRICES=true` in the live env file before building images, then rebuild the storefront. Prices and add-to-cart are hidden until the customer signs in.
</Tip>

## After golive

* Run `pnpm vulpy env status live` and `pnpm vulpy env doctor live` for post-cutover checks.
* Confirm `www.` and the preview host both 301 to the apex.
* Confirm Matomo receives traffic after a visitor accepts analytics consent on the storefront.

<CardGroup cols={2}>
  <Card title="Backup and restore" icon="database" href="/deploy/backup-restore">
    Snapshot the live environment before any migration or major change.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/shop/analytics">
    Consent, PII rules, and event helpers for Matomo on live.
  </Card>
</CardGroup>