Deploy from CLI

Learn to deploy revenexx Storefronts from the revenexx CLI.

revenexx Storefronts allows you to host and deploy storefronts directly within the revenexx platform. Each site can have many deployments, which can be thought of as versions of the web application.

While we recommend you create deployments through automatic Git deployments, you can also create deployments via the revenexx CLI.

CLI

You can deploy a storefront from the CLI without opening the Console.

Before proceeding

Install the CLI, sign in with your API key, and select your tenant with revenexx tenants use <slug>. You also need the site's ID — create the site in the Console or with revenexx sites create, then list your sites with revenexx sites list.

Create a deployment from your storefront code. --code . packages the current directory; --activate true makes the new build live as soon as it finishes:

Shell
revenexx sites create-deployment --site-id <SITE_ID> --activate true --code .

If you didn't activate on create, switch the site to a finished deployment by its ID:

Shell
revenexx sites update-site-deployment --site-id <SITE_ID> --deployment-id <DEPLOYMENT_ID>

Review the deployment history, or roll back by activating an earlier one:

Shell
revenexx sites list-deployments --site-id <SITE_ID>

For a site connected to a Git repository, deploy from a branch or commit instead of uploading code — this is the recommended path, covered in Git deployments:

Shell
revenexx sites create-vcs-deployment --site-id <SITE_ID> --type branch --reference main --activate true

Flags vary per command — run revenexx sites <command> --help for the authoritative list.

See also: Learn more about the CLI service commands

Configure CLI deployments

The CLI has no revenexx.config.json and no project file. To target a different endpoint or tenant, sign in with revenexx login --token <API_KEY> --tenant <slug>, switch tenants with revenexx tenants use <slug>, or set REVENEXX_API_KEY, REVENEXX_TENANT, and REVENEXX_API_URL in your environment. Build settings — install command, output directory, framework — belong to the site itself and are set with revenexx sites update or in the Console.

See also: CLI configuration

Debugging

  • If you updated your storefront's configuration but the deployment is not working as expected, you may need to create a fresh deployment before the changes take effect.
Was this page helpful?