Configure your project

The Adobe Commerce on cloud infrastructure Project Web Interface enables you to do the following for all Starter and Pro environments:

• Access projects
• Add users and manage access
• Manage Git branches

As you make changes to these settings, the branch redeploys to the environment. You can make these setting changes for all Starter and Pro environments.

Access your project and environments

The Project Web Interface provides several ways to access your project and environments:

• Storefront URL for each active environment
• Secure Shell (SSH) link for SSH access via terminal application
• Clone the project using the Magento Cloud CLI or Git

To access projects and environments through the Project Web Interface:

1. Log in to your project.

2. Click Access Project for a list of URLs and SSH.

   

For more information about using SSH, see SSH to an environment. To clone the project using either the Adobe Commerce on cloud infrastructure CLI or Git, use the links in the field under the branch name.

The following figure shows an example.

Click either CLI or Git to display the appropriate clone command. Use the (Copy to clipboard) button to copy the command to the clipboard.

Configure environment settings

You can set the following configuration options for each environment:

Configure emails for testing

One of these environment variables enables or disables outgoing emails for the environment. If you wanted to test email notifications for the environment, you need to set this option On.

1. Access your project and select a specific environment.
2. Select the Settings tab.

3. For the Outgoing emails option, select the toggle to On.

   

Configure your email notifications, services, and more as needed through the Admin and test emails.

Set environment and project variables

You can set project wide and environment specific variables through the Project Web Interface. Variables can be either text or JSON format. For more information, see Environment variables.

For an example of variables, we walk you through creating Admin variables through Onboarding and project creation tasks. You may want to add environment variables for sensitive data like payment method information. Project variables are set across all branches and environments.

To view or edit environment variables, you must have at minimum the project reader role with environment admin privileges.

If you want to add the same variables to your Integration, Staging, and Production environments, we recommend adding all of the variables one at a time to the Integration environment. After you finish adding variables, push the changes to the Staging and Production environments.

Environment variable

To set environment specific variables in the Project Web Interface:

1. Access your project and select a specific environment.
2. Select the Variables tab.
3. Click Add Variable.
4. In the Name field, enter a variable name. For example, to set the Admin default account password, enter ADMIN_PASSWORD.

5. In the Value field, enter the value for the variable. For example, enter a valid email address accessible for reset email notifications.

   

6. As needed, select options for JSON value, Enabled, Inheritable by child environments and Sensitive. If you do not have Super User access, you may only see the JSON value option.
7. Click Add Variable. After you add the variable, the environment will deploy. Wait until deployment completes before more edits.

If you are attempting to override configuration settings, you must prepend env: to the variable name. For example:

Project variable

To set project variables in the Project Web Interface:

1. Access your project and select a specific environment.
2. Select the Variables tab.
3. Click Add Variable.
4. In the Name field, enter a variable name. For example, to set the Admin email for the default account, enter ADMIN_EMAIL.

5. In the Value field, enter the value for the variable. For example, enter a valid email address accessible for reset email notifications.

   

6. As needed, select options for JSON value, Visible during build, and Visible during runtime. If you do not have Super User access, you may only see the JSON value option.
7. Click Add Variable. After you add the variable, the environment will deploy. Wait until deployment completes before more edits.

Configure routes

Routes allow you to set redirects or upstream settings for applications for your specific environment. For full details on routes, see routes.yaml. These routes (or URLs) are used to access your storefront.

1. Access your project and select a specific environment.
2. Select the Routes tab.
3. Select Add Route.
4. Enter a URL. You can use {default} in the URL, which is a placeholder for the default domain.
5. Select a Type: Upstream for applications or Redirect.

6. To configure an Upstream route:

   1. Enter the Upstream route.
   2. Use the toggle to enable or disable the Cache for the route.
   3. Enter the cookies to list: No cookies, All cookies, or Specify a specific cookie. You can enter multiple specific cookies.
   4. To add Headers to an allowlist, select Default Headers or Specify a header. You can enter multiple headers.
   5. Use the toggle to enable or disable the Server-Side Includes (SSI).
7. To configure a Redirect, enter a URL to Redirect to. You can use {default} in the URL, which is a placeholder for the default domain.

8. Click Add Route to save. The setting is saved and deployed to the environment.

   

View environment history

An environment’s history includes:

• Initial creation
• Snapshots
• Syncs and merges
• Code pushes

To view the history for an environment, log in to your project and select the environment. The page displays a general history of actions completed on the page. For a detailed list of completed actions during build and deployment, we recommend reviewing logs directly on the servers. See View logs.

The following figure shows a sample history.

The history shows, from oldest to newest:

• Environment branched from FeatureX
• Environment synced with the parent
• Environment snapshot created

We recommend creating a snapshot before you make any code changes.

• Environment variable added
• Environment snapshot created