Provide your Colony members with all the dev/test environments they need. Develop a blueprint that models an application stack in a specific configuration, and publish it to the self-service Blueprints Catalog. Your space members can then independently launch environment sandboxes as needed.
Blueprints are defined in source-controlled YAML files. For example, a LAMP stack web application based on Apache, MySQL and PHP may be deployed in two flavors which are represented as two different blueprints:
Blueprint A: A single server that includes all the applications and is used from the CI to run sanity tests and provide fast feedback to the developers.
Blueprint B: A complex production-like environment with multiple front-end servers behind a load-balancer, that serves as a staging or demo environment for final tests.
To add a new blueprint to your space:
For step by step instructions on how to develop your CloudShell Colony blueprint, see Steps to Developing a Blueprint.