At the completion of this section, you will:
- understand the use of environments in FlexDeploy
- be able to create/modify an environment
An Environment is a logical name given to a group of servers, applications, and technologies which work together to provide a software solution for the purpose of development, testing, or a production implementation. Typical Environments include, but are not limited to, Development (DEV), System Integration Testing (SIT), User Acceptance Testing (UAT), and Production (PROD).
For this tutorial we will create four environments - Development, Test, QA, and Production. These environments host our physical EBS installations for our logical global EBS instance.
| Tip | ||
|---|---|---|
| ||
We will deploy our customizations into Test, QA, and Production. Since development typically occurs directly in the Development environment it would not make sense to deploy there. For web applications, deploying into Development makes much more sense. For EBS, we will execute our builds in the Development environment. This would allow us to extract the customizations for from the Development EBS during the build phase. For the example in this tutorial we will source all of the customizations from GitHub, so technically we could execute our builds anywhere. |
You can view the list of defined environments by selecting Topology from the menu, and then selecting the Environments tab from the left-hand pane. There are no environments with a new installation, so next we will create them.
...
| Completed 5 of 10 Sections | Continue to Instance Creation | Back to Endpoint Creation |
|---|