Manage your project

The Magento Commerce (Cloud) project includes all code in Git branches, associated environments, and applications. Applications have environments and services that run on them including a database, web server, and caching server.

We provide a Project Web Interface and CLI commands to fully manage all aspects of your project. You have full access to all environments for Starter and Pro environments. You may need to continue to use SSH and CLI commands for some aspects of Pro plan Staging and Production environments.

Updating your Pro project: These sections include instructions for Pro projects with Staging and Production available in the Project Web Interface. To add Staging and Production to your interface, see Add Staging and Production to Pro projects UI.

We can update Pro projects created before October 23, 2017. All new Pro projects include these features. Your ticket will be queued for update, which may take time to complete. We will keep you updated through the process.

If you do not request this update, you must submit tickets to modify settings, variables, routes, and more for Pro plan Staging and Production environments.

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

Project and environment variables

The following sections detail more about project and environment variables:

Upgrade and patch

To upgrade and patch Magento, see:

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.

Log in to a project

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.

    Go to account settings

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

    View your project details

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

    Your Blackfire 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.

Starter branch hierarchy

For Pro, you will see a hierarchy of branches starting from Production to Staging to Integration. The Enterprise icon 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.

Pro branch hierarchy

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.

Pro branch hierarchy (original)

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.

Access your project

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.

Show or hide inactive branches

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.

Access your project

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

configure environments

Configure the project

Click edit project (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).

configure project