Skip to main content
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.
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?”

​
Steps

1

Add the live environment

Run this on the VPS as the deploy user (sudo -iu vulpy-commerce):
The command adds domains, builds and starts services, and runs Matomo setup as part of the flow.
2

Point DNS

Create records for the four live hostnames. Defaults are labels; you can override them via install flags.
3

Verify Matomo

Run the privacy and legal gate check. Golive refuses without it.
4

Cut over

Promote preview to apex:
On success, the preview host 301s to the apex and the shop is public.
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.
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.

​
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.

Backup and restore

Snapshot the live environment before any migration or major change.

Analytics

Consent, PII rules, and event helpers for Matomo on live.