Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Return

How to properly use multiple environments

Keep separate settings for development and production so you can test safely.

Steps at a glance ​

  1. Use the Editor environment to build and test, and Production for your live app (plus Staging if your plan includes it).
  2. Put different keys and URLs in each environment.
  3. Test in the editor (or on staging), then publish to production.

1) Decide what changes per environment ​

Common examples:

  • Database or API base URLs
  • SSO Providers settings
  • Email provider keys

2) Store environment-specific values ​

  1. Open the Settings tab, then open Environment Variables.
  2. In the Custom tab, click Insert and enter a Name (for example PAYMENT_API_KEY).
  3. Enter the value for Editor (used while you build and preview) and the value for Production, then click Insert. If your project has a staging environment, you can also enter a Staging value.
The Add Environment Variable window with the Name, Editor and Production fields and the Insert button

Learn more about environment variables →

3) Test correctly ​

  • Always test new changes in development first.
  • When you click Publish, check where you publish to. If your plan includes staging, use Publish to staging first, then Publish to production once the staging version works.

Learn more about publishing →

Common pitfalls ​

It works in development but not in production ​

  • The production environment might be missing a value (key, URL, or allowed domain).