Post on 20-Jan-2017
Managing CloudHub Specific Settings
2
Managing Regions
If Global Deployment is enabled on your account, you can also set the
Default Region. The region auto-populates in the deployment screen
settings for all applications deployed by users in your organization, and it
can be adjusted at the application level if necessary for individual
deployments. Access this menu by clicking the gear icon next to your user
name at the top of the screen and then picking the General link, under
CLOUDHUB in the left menu.
3
4
Managing Environments
CloudHub gives you the ability to create separate environments for deploying, these are independent from each other. Environments can either be of production or sandbox type. By default, when creating a new organization you get one production environment named Production.
Sandbox environments are helpfully restrictive environments for developers and testers, they facilitate safe testing of applications without the risk of affecting the production environment.
5
For example, you can create a sandbox environment for a QA team in which they can test new releases of applications before deploying in production. You can add users to a sandbox environment without permitting them to access the production environment, thereby securing production and eliminating the risk of a developer accidentally operating upon an application in production. After you are sure an application is safe to expose to users, you can easily promote the application from a sandbox environment to a production environment.
6
7
CloudHub Subscription
When you first sign up for CloudHub, you’re automatically added to the Free plan (subscription level). To upgrade to a paid plan, contact your account executive or cloudhub-support@mulesoft.com.
To see your subscription level and usage, click the gear icon at the top of the screen and click Subscription:
8