To create a new environment click on "Environments" on the left sidebar under the "Manage" section. A new stack will have to be created first if none exist or if you need to have your environment under a specific stack.
***Note that stacks do not influence the type of environments that you can create or manage. They are merely a way to organize your environments.
To create a new stack click on "Actions" -> "Create new stack"
You will next be prompted to give your stack a name and an optional description:
Once the new stack is created, the new environment can be created by clicking on :
You will then be taken to the environment creation page where you will name your new environment, chose the location of the datacenter and type of infrastructure. The latter can be either "Single Instance" or "Load Balanced". The type of instance is based on the Server Class of your choice which can be "General Purpose" or "Compute Optimized". Once chosen one of the two options, you can specify the server size which is based on the number of CPUs. As such, each server size will produce its own list of instances available for selection. These instances are specific for the cloud provider of your choice. Only one instance can be selected before going to the next step.
Note that if selecting "Load Balanced" Infrastructure type, the number of instances will also have to to be specified:
Clicking on will lead through each of the 6 steps.
The second step is dedicated to provisioning. This is done by first choosing the desired operating system from the ones that are available. After that, you have the option of either choosing one or none of the single or pre-prepared combination of packages, such that they will be available as soon as the environment is created. For this example, we will chose Ubuntu 16.04 Xenial as the operating system along with the LAMP stack (PHP, Apache and Mysql):
Note that only one of the available packages/package stacks can be selected at this faze. Additional packages can be added once the environment is created.
Also, some packages (like Mysql) will require a mandatory root password in the bottom left corner of the page.
Next, on the disks screen, the mandatory root disk is visible and there is also the option of adding other volumes by hitting .
On step 4, the security rules can be configured to specific preferences.There will always be a default configuration available:
On step 5 there are the authentication parameters. This is where the pre-added ssh keys from the "Environment Resources" can be selected from the drop-down list so that they can be included in the environment:
Finally, on step 6, there is a summary of the selected environment parameters. Any of them can be modified by clicking directly to the desired step.
Simply hit to start building your environment. The progress can be tracked by hitting the "View Logs" link on the top yellow band from the resulting environment page. Alternatively, the logs can be viewed by going to "Environment Deployments" on the environment side-bar.
Both these actions will permit access to the deployer and session logs where the progress can be tracked in real-time: