Separating Development and Production Environments

We're excited to announce a new feature in Essepage that makes it easier to separate your development and production environments.

As developers know, it's standard practice to use development APIs and databases during the build process, while switching to production resources for live services. Until now, Essepage had this capability, but we've completely redesigned it to be more intuitive and user-friendly.

From now on, when you're working in the Essepage editor, you will be in the Development environment. After you apply changes, the actual page becomes the Production environment.

To support this clear distinction, Essepage now offers the following syntax:

<div>
    {{@dev: development code [@prod] production code :@}}
    {{@prod: production code [@dev] development code :@}}
</div>

With this setup, your preview displays the development code while you're working, and the actual page shows the production code after you apply your changes.

This powerful feature can also be used in both +essepage.config.json and +global.config.json configuration files.

For example, if you want to use different payment APIs across environments in your +global.config.json, you can configure it like this:

{
  "payment_api": "{{@dev: https://test.pay.com/xxx/yyy [@prod] https://pay.com/xxx/yyy :@}}"
}

For those using Essepage's authentication features, you can now configure the +essepage.config.json file with environment-specific values:

{
  "auth_salt":                 "{{@dev: DEV_AUTH_SALT [@prod] PROD_AUTH_SALT :@}}",
  "token_salt":                "{{@dev: DEV_TOKEN_SALT [@prod] PROD_TOKEN_SALT :@}}",
  "refresh_token_max_age":     "{{@dev: 3600 [@prod] 2678400 :@}}",
  "access_token_max_age":      "{{@dev: 10 [@prod] 3600 :@}}"
}

This feature is available starting today and applies to all Essepage projects. We can't wait to see how it improves your development workflow!