To redeploy a storefront that was created in Business Manager after initial deployment, use the Storefront Next CLI and the autocreated MRT project and environment.
package.json, run the pnpm install command.In Business Manager, navigate to your storefront. Click App Launcher 
, then select Administration > Sites > Storefronts, and click your storefront.
In the storefront detail page, click your environment, and then next to Deployments, click Manage.
If you have an .env file in your storefront with the project ID (MRT_PROJECT) and environment ID (MRT_TARGET), skip this step. Otherwise, get these values from Runtime Admin.
a. To get the environment ID, click Environment Settings, and copy the Environment ID value.
b. To get the project ID, click the project name, then Project Settings, and copy the Project ID value.
To authenticate the CLI to Managed Runtime, use an API key. Get the Managed Runtime API key in Managed Runtime Admin. In Account Settings, under Personal API Key:
a. If you haven’t yet created an API key, click Generate.
b. If you already have an API key, the value is partially masked. Click Reset, then click Reset my API Key when asked for confirmation.
c. Run this command to save the API key locally in the ~/.mobify file so it can be reused whenever you run the pnpm sfnext push command. Replace the placeholder values in this command before running it.
1b2c mrt save-credentials --user {your-email@example.com} --api-key {your-mrt-api-key}We recommend saving the MRT API key credentials. If you don’t save the MRT API key, you can add the API key in the MRT_API_KEY variable in the .env file or supply it in the --api-key argument on the command line. See MRT API Key in the Agentic B2C Developer Toolkit.
Note
From your local storefront folder, use this command to create a bundle and deploy it to your Managed Runtime environment. Replace the placeholders with the MRT project ID, target environment, and the API key you got earlier.
1pnpm sfnext push --project {mrt-project-id} --environment {target-env}
2--message "Deploying quick start bundle."Always run pnpm sfnext push from the local storefront folder. To run the push command from another folder outside your storefront, use pnpm dlx @salesforce/storefront-next-dev push instead and pass in the storefront folder path with --project-directory {sfnext-project-folder}.
Tip
The .env file in your Storefront Next project folder contains environment variables that the Storefront Next CLI uses. You can set the project ID in the MRT_PROJECT variable and the target environment in the MRT_TARGET variable. If you specify these values in both the command line and the .env file, the command line arguments are used.
To upload only the bundle to MRT and not deploy it, don’t specify the --environment option and remove the MRT_TARGET variables from the .env file.
Note
Verify that the bundle was deployed to the target environment. In Managed Runtime Admin, in Projects, click your project and then your environment.
j