Deployments

Oxygen automatically makes its first deployment when you create a new storefront.

You can make additional deployments by creating commits and pushing them to your connected repository. Every push triggers a new deployment.

By default, each deployment is private, which means that you need to be logged into your store to view it. You can make individual deployments public, which means that anyone with the deployment URL can view it.

To prevent search engines from incorrectly indexing any preview deployments, the robots.txt file in any non-production public deployment is overridden with a disallow rule.

1. In your Hydrogen storefront, open the deployment details page for the deployment that you want to update.
2. Click Actions.
3. Click Make deployment public or Make deployment private.

Changing deployment visibility can take up to 15 seconds.

By default, environment URLs point to the environment’s most recent deployment.

If the most recent update contains a bug or other error, you can temporarily roll back to a previous deployment while you work on a fix. Rolling back doesn't redeploy or delete any deployments; it simply changes which deployment the environment URL points to.

Only production and custom environments can be rolled back.

1. On your Hydrogen storefront overview page, click … on the environment to roll back.
2. Click View deployments.
3. In the list of deployments, click … beside the deployment to roll back to.
4. Click Make this the current deployment.
5. Click Make current for {Environment} to confirm.

The next time that you push an update to its linked branch, the environment will return to the default behavior of pointing to the most recent deployment.

Every deployment in Oxygen is immutable, which means that a deployment is a snapshot of a single Git commit in your Hydrogen app codebase, at a specific point in time.

Deployments also retain all the environment variables that they had at the time they were deployed. Whenever you update an environment variable, push a commit to the relevant branch to trigger a new deployment.