Tutorial: Creating a deployment¶

The objective of this tutorial is to guide you through the deployment of a prepared package; either one prepared by Elastycloud or one prepared by you.

Prerequisites¶

You have to be a registered partner of Elastycloud.
You need to have an account and be able to sign in to the Elastycloud Console.
You need at least one database server provisioned.
You need at least one domain connected.

Tutorial¶

Sign in to the Elastycloud Console.
Go to Installations in the menu.
Press the + button (Add installation) near the top right corner of the page.
Fill in the form with the necessary information. See: Installation details
Press the Save button in the dialog box.
Go to Deployments in the menu.
As for the installation, press the + button near the top right corner.
Fill in this form with the necessary information. See: Deployment details
Press the Save button in the dialog box.

If the deployment details are filled in correctly, the installation will be triggered within a minute. You can see the state of a deployment in the list of deployments (in the State column). You can also find a list of events on the History page (press the History item in the main menu).

Installation details¶

An "installation" is the top level entity for a specific website, you will normally have one installation for each of your customers. Every installation can then have any number of staging deployments, but only one "production" deployment.

Name: The name you use to identify your customer. This value is used internally in the Elastycloud Console, and shows up on your invoice.
Identifier key: This is the real identifier of the installation, it has to be globally unique, and can not be changed after the installation is saved. This will also show up on your invoice.
Status: Defines the payment/subscription status of the installation. Note: This does not currently affect the deployments.; TODO: What is the difference? What is the purpose?

Deployment details¶

A deployment is the entity that controls one specific Magento 2 installation in the Elastycloud. Here you define the type of the deployment, what code, and what version you want the deployment to run.

Installation: Choose which installation you want the deployment running under.
Name: Use this to differentiate between different deployments. This shows up on your invoice.
Primary domain: Set the domain you want to associate with the (private) Magento administration panel for the deployment.
Secondary domain: Set the public facing domain associated with the deployment.
Admin path: Choose the path to use for the admin page for the deployment. You can use the default value, since this is a randomly generated value for the sake of security.
Profile: Select an appropriate deployment profile to use.
Package: Choose which package you want this deployment to run. The list contains all the packages you currently have access to; this includes both your own packages and packages maintained by Elastycloud.
Package version: Pick the desired package version, or leave blank for the currently preferred default stable version.
Type: This defines how the deployment will be treated (Production or Testing), and helps you identify deployments in the Deployment list. Production deployments get automatic monitoring and are allowed to run live stores. NOTE: You can have a maximum of one production deployment per installation. This cannot be changed after creation.
Database: Select the database server that you want your deployment to use. Note: This can not be changed after the deployment has been created.
Cluster: Select the cluster on which your deployment should run. Note: This can not be changed after the deployment has been created.