Manage your project

To manage your project, environment, and branches, see:

• Configure your project
• Project structure
• Create and manage users
• Manage branches with the Project Web Interface or CLI commands
• Snapshots and backup management

Project and environment variables

The following sections detail more about project and environment variables:

• Overview of environment variables
• Magento Commerce (Cloud) environment variables
• Magento application environment variables
• Configuration management
• Example of configuration management

Upgrade and patch

To upgrade and patch Magento, see:

• Upgrade and test Magento Commerce
• Patch and test Magento Commerce

Access the Project Web Interface

With your Magento Commerce (Cloud) account created, you can log into the Project Web Interface at https://accounts.magento.cloud.

Blackfire and New Relic credentials

Your project includes Blackfire and New Relic services. The project details display information for your project plan and important licenses and tokens for these integrations. Only the Account Owner has initial access to the credentials and services. You should provide these credentials to technical and developer resources as needed.

• Blackfire.io Profiler provides tools for reviewing and optimizing Magento and your store in your environments. The profiler checks every method and call, determining what occurs with performance metrics per step.
• New Relic APM provides application metrics and performance information for Staging and Production environments. This service is not the module or extension and does not provide infrastructure (hardware) monitoring. Do not install the New Relic module with this service in Magento Commerce (Cloud).

To review your integration tokens, IDs, and more:

1. As the Magento Commerce (Cloud) Account Owner, log in to your Magento Commerce project.

2. In the upper right corner, click <your name> > Account Settings.

   

3. On your account page, click View Details for your project to open general settings and plan details.

   

4. On your project details page, scroll to and expand Blackfire and New Relic to review your credentials.

   

Access the project and environments

When you first login, a list of projects you have access to displays. As a Project Owner, you may only see your company’s project. A Magento Solution Partner may see multiple projects for all of the clients they support.

Click on a project to access branches and more. On the page, you will see a hierarchy of environments named by the Git branch.

For Starter, you will see a hierarchy of branches starting from Master (Production). Any branches you create display as children from Master. We recommend creating a Staging branch, then branching from that for your Integration development. For more information, see Starter architecture.

For Pro, you will see a hierarchy of branches starting from Production to Staging to Integration. The icon indicates these branches deploy to a dedicated server, used by Staging and Production. Any branches you create display as children from Integration. For more information, see Pro architecture.

The following table details the branches for Pro:

Branch	Environment	Description
(no branch)	Global Master	This "branch" captures global project changes including adding user accounts and variables. Important: Do not create branches from or merge to Global Master.
production	Production	This is a child branch from master with a deployment target. You cannot branch from this branch. You merge code from master to this branch to go live with updated configurations and code.
staging	Staging	This is a child branch from master with a deployment target. You cannot branch from this branch. You merge code from master to this branch to test in a pre-production environment.
master	Integration master	The master branch of the single repository. In the Project Web Interface, this is called Integration. You branch from master for your development on your local, generating an environment when you push code. When this code is complete, you merge to staging and production.

If you are an existing Pro merchant, and have not ticketed to add Staging and Production to your UI, you will see only Integration master and any created branches.

To access an environment store and admin, select a branch and click Access Site. A list of store URLs and SSH command display. Select the URL to view the store in that environment.

The Pro plan Production environment includes three nodes that you can access using the following links:

• Load balancer URL: http[s]://<your domain>.c.<project ID>.ent.magento.cloud

• Direct access to one of the three redundant servers: http[s]://<your domain>.{1|2|3}.<project ID>.ent.magento.cloud

  The production URL is used by the content delivery network (CDN).

If you have inactive Git branches of code, you can toggle displaying the branches in the hierarchy.

Configure environments

You can manage variables and settings for Production, Staging, and Integration environments through this interface, or with CLI commands. Click Configure environment to create and manage environments, each of which corresponds to a Git branch.

This displays the following page, which enables you to configure settings, [variables](/documentation/magento_doc/guides/v2.2/cloud/project/project-conf-files_magento-app.html, routes, and users.

Configure the project

Click (edit) to display users and deploy keys associated with the project. You can modify access and permissions across the entire project and per environment (or branch).