Skip to content
Atlas Platform

Add an Environment to Atlas App

Once you’ve gone through the steps here, you’ll have a new environment, on your existing an Atlas app, that has been deployed to the web.


Once you have Created an Atlas App then you will have a default environment visible on that app, but you can then add another environment. In fact you can add up to 3 environments per Atlas app, so you can add up to 2 more via the Add environment button shown below. Add environment to App

Completing the Add Environment Form

This form deviates slightly from the Create App step for adding an environment, but the results are the same: a deployed Atlas environment, linked to a WordPress headless backend, and relying on a Repository Provider (GitHub, Bitbucket, GitLab - unless zip-uploaded).

Once you have clicked Add environment you will be taken to the following Add Environment form. Add Env Form

Name Your Environment

Enter a name for your Atlas environment. The name should represent how you intend to use the environment. For example, enter something like prod if it’s a production environment, staging if it’s a staging environment, etc.

Ensure Repository Provider is Connected

The previous Atlas app creation stage will have set what Repository Provider & Repository is to be associated with an Atlas app - each environment, however, may use different branches from the connected Repository. Occassionally the connection between Portal and the Repository Provider will expire & you will see that the Connected green icon will disappear, in favor of a Reconnect button. Click this and follow the steps if you need to reconnect.

Reconnect Repository Provider

Select a Branch

From the list of your repository’s branches, select the branch you want to base your environment on. Whenever changes are pushed to this branch, your app will be automatically re-deployed.


  • If you want to create a production environment, you could use your repo’s main branch
  • If you want to create a staging environment, you could use your repository’s staging branch

Select a branch

Verify Your Project Directory

If your project is stored in a folder within your repository, specify the path to your root folder by clicking on the Edit button in the Root Directory field.

Select the subfolder

Connect WordPress Environment

Every headless environment is associated with a WordPress environment. Choose either:

  • I already have a WordPress environment: Use a WordPress site from your WP Engine account. Select the search bar and search for the name of your WordPress site.
  • I want to create a new WordPress install: WP Engine makes a new WordPress site and links it to your application. In the box, enter a name for your new WordPress site.

Link to WordPress

Install Headless Plugins

In order for your WordPress environment to become “headless”, Atlas can install the WPGraphQL, Faust.js and WP Engine Atlas Headless Extension plugins, as also shown above.

Set Environment Variables (Optional)

To add environment variables for your environment, click Add environment variables (Optional).

Enter the Key and Value pairs for each environment variable.

Link to Environment Variables

For example, you may need to add a NEXT_PUBLIC_WORDPRESS_URL key with a URL as its value to specify which WordPress site should be used as the data source for the app. You may also need to specify additional environment variables to store sensitive data such as API keys and secrets.

Please refer to your JavaScript framework’s documentation if you’re unsure what environment variables are required for your app.

Select Create.

Assuming all the required fields are populated and valid you will now be able to click Create to create your new environment.

The Atlas app’s Environment Details page appears upon completion of the environment create form. When Atlas completes building your headless enviroment, a checkmark & status message of success appears in the Last deployment card.

Was this page helpful?
👍 Yes  |  👎 No