Docs Menu

Docs HomeAtlas App Services

App Environments

On this page

  • Environments in Atlas App Services
  • Supported Environments
  • Environment Values
  • Environments in Workflows
  • Use Environments in CI/CD

In App Services, an environment represents a collection of environment values that corresponds with a stage in your development process. For example, many organizations use different environment values for Development and Production.

When you deploy an App, you can specify the environment that this application represents. If you do not specify the environment, the App defaults to No Environment.


Setting your App's environment tells App Services which environment values to use. When you change the environment, this changes the environment values that the App uses. This is distinct from the more general values, which do not change when you change the app environment.

App Services supports the following environments:

  • ""

  • "development"

  • "testing"

  • "qa"

  • "production"

You can define environment values directly in the App Services UI. You can also import environment configuration files with Realm CLI or GitHub. In these files, you define environment values as JSONobjects.

These values are specific to the environment that the app represents. For example, you'd store your Production environment values in a production.json file in the /environments directory, and your Development environment values in a development.json file. When you specify the environment for your App, App Services uses the corresponding environment values.

Each App represents a single environment in your development process. This means that a typical development process is likely to have a minimum of three Apps at any given time; Development, Testing, and Production. If you use unique applications to test different feature branches, you might have many versions of Development and Testing apps -- one for each branch.

Diagram showing different App Services Apps for each branch
click to enlarge

You can use environments in your CI/CD pipeline. You might create an automated process to generate a new Testing app when a developer on your team opens a pull request to merge development work to staging. You can use realm-cli to automate creating a new App, setting the environment to testing, and importing your updated app configuration.


See also:

For a complete example CI/CD pipeline that manages testing, deployment, and other tasks for a real application, see: How to Build CI/CD Pipelines for App Services Apps using GitHub Actions.

←  Make a Copy of an AppChange Environments →
Share Feedback
© 2022 MongoDB, Inc.


  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2022 MongoDB, Inc.