project-webint-basic.md

layout	group	subgroup	title	menu_title	menu_order	menu_node	level3_menu_node	level3_subgroup	version	github_link
default	cloud	100_project	Basic project information	Basic project information	21		level3child	project	2.0	cloud/project/project-webint-basic.md

Log in to your project {#project-login}

The Web Interface {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %} for your project is available in the following ways:

• Your welcome e-mail
• The Magento Enterprise Cloud Edition command-line interface (CLI)

{% collapsibleh3 Find the project URL using the CLI %}

To find the project URL using the CLI:

1. Log in to the machine on which your SSH keys are stored.

2. Log in to your project:

   magento-cloud login
   

3. Enter the following command:

   magento-cloud project:list
   

   A sample result follows:

   Your projects are:
   
   +---------------+--------------+---------------------------------------------------+
   | ID            | Title        | URL                                               |
   +---------------+--------------+---------------------------------------------------+
   | pwga254dhx97o | Magento 2    | https://us.magento.cloud/#/projects/pwga254dhx97o |
   +---------------+--------------+---------------------------------------------------+
   

4. Enter the value in the URL column in a web browser. {% endcollapsibleh3 %}

Log in to the project

In a web browser, enter the project URL from your welcome e-mail or that you found using the CLI. When prompted, log in to your project using Bitbucket, GitHub, Google, or a e-mail address and password.

{% collapsible Click to show/hide image %}

{:width="450px"} {% endcollapsible %}

Access your project and environments {#project-access}

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

• Your {% glossarytooltip 1a70d3ac-6bd9-475a-8937-5f80ca785c14 %}storefront{% endglossarytooltip %} URL (every environment, or branch, has a different URL)
• Secure Shell (SSH), a way to interact with services using a command terminal
• Clone the project using the Magento Enterprise Cloud Edition CLI
• Clone the project using Git

{% collapsible To access projects and environments: %}

1. Log in to your project.

2. Hover the mouse pointer over Access Project as the following figure shows:

   {:width="600px"}

3. For example, to view your storefront, click the Web Access link.

   For more information about using SSH, see SSH to an environment.

4. To clone the project using either the Magento Enterprise Cloud Edition CLI or Git, use the links in the field under the branch name.

   The following figure shows an example.

   {:width="600px"}

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

{% endcollapsible %}

Get started configuring your project {#project-conf}

Configuring a project means:

• Managing users
• Using a deploy key to pull code from a private repository

{% collapsible To configure your project: %}

1. Log in to your project.

2. Click  (Configure project) next to the project name.

3. See one of the following for more information:

   • Manage users
   • Pull code from a private Git repository

{% endcollapsible %}

Get started configuring an environment {#project-conf-env}

Configuring an environment means:

• Environment settings
• Configuring environment variables
• Configuring routes
• Managing users

{% collapsible To configure an environment: %}

1. Log in to your project.

2. Click Configure environment under the project name, as the following figure shows.

   {:width="500px"}

3. See one of the following for more information:

   • Environment settings
   • Set environment variables
   • Configure routes
   • Manage users

Environment settings {#project-conf-env-set}

The following table shows available environment settings.

Option	Description
Environment status	An environment can be either active or inactive. You'll do most of your work in an active environment. After merging an environment with its parent, you can optionally delete the environment, making it inactive. To delete an environment, click Delete. You can active an inactive environment later.
Outgoing emails	Setting to On means that code in your environment can send and receive e-mails (for example, using PHP email() function.
HTTP access control	Setting to On enables you to configure security for the project's Web Interface using a login and also IP address access control.

Set environment variables {#project-conf-env-var}

As discussed in Overview of environment variables, environment variables are settings specific to an environment. Variables can be either text or JSON format.

To view or edit environment variables, you must have at minimum the project reader role with [environment admin]({{ page.baseurl }}cloud/project/user-admin.html#cloud-role-env) privileges.

For example, you can change the Magento Admin administrative password using environment variables as follows:

1. Click Add Variable.

2. In the Name field, enter ADMIN_PASSWORD.

3. In the Value field, enter the administrator's password.

   The following figure shows an example.

   

4. Click Add Variable.

5. Wait while the environment deploys.

Configure routes {#project-conf-env-route}

As discussed in routes.yaml, routes (or URLs) used to access your Magento storefront. See that section for details about what the options mean.

The following figure shows an example.


{% endcollapsible %}

View environment history {#project-conf-hist}

An environment's history includes:

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

{% collapsible To view an environment's history: %}

1. Log in to your project.

2. In the left pane, click the name of an environment.

   The following figure shows a sample history.

   {:width="600px"}

   The history shows, from oldest to newest:

   • Environment branched from FeatureX

   • Environment sync'd with the parent

   • Environment snapshot created

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

   • Environment variable added

   • Environment snapshot created

{% endcollapsible %}

Related topics

• Manage environments (branches)
• Project backup and restore (snapshot)
• Get started with a project