Deploying to Surge

Prerequisites

Before you get started, you need to have:

• A Surge account, using the surge CLI.
• A commercetools account and a Project.
• A Custom View configured in the Merchant Center.

Configuration

In your Custom View config, provide the Custom View ID you got when you configured the Custom View in the Merchant Center.

Moreover, you need to provide the production URL from your Surge project. You can keep the standard Surge URL https://<project>.surge.sh or provide your custom domain.

{
  "env": {
    "production": {
      "customViewId": "ckvtahxl90097sys6har1e6n3",
      "url": "https://<project>.surge.sh"
    }
  }
}

Using environment variables

In case you want to avoid hardcoding certain values, for example the Custom View ID, or the Project key, you can use variable placeholders in your Custom View config.

{
  "env": {
    "production": {
      "customViewId": "${env:CUSTOM_VIEW_ID}",
      "url": "https://<project>.surge.sh"
    }
  }
}

Production bundles

The main command to create the production bundles is mc-scripts build. The output folder is public, which is what is going to be uploaded to Surge.
See Going to production for more information.

Deploying to Surge

Use the Surge CLI to upload the static files.

surge public https://<project>.surge.sh

That's it!

Test your deployment

In the Merchant Center you can now follow the steps to install the Custom View and access it in your Projects.