Every space in CloudShell Colony is associated with a source-controlled Blueprint Repository. Blueprint files, application files, scripts and additional assets, such as configuration and health check scripts, make up the repository.
In this article:
For reference, see our sample repository on GitHub: https://github.com/cloudshell-colony/samples
A repository includes two folders:
- Blueprints: Consists of the blueprint's YAML files.
To learn more about the content of the YAML files see The Blueprint's YAML File.
- Applications: Consists of all the applications you modeled. Each application is stored in its own subfolder and includes relevant application YAML files and optional deployment scripts.
To learn more about the application's YAML file see The Application's YAML File.
Applications can optionally include additional scripts that run as part of deploying and configuring applications in a sandbox. Learn more about Application Scripts.
- Services: Your blueprint can optionally include managed infrastructure services. If you choose to include services in your blueprints, make sure to create a designated services folder for them. To learn more about creating Managed Infrastructure Services, see Integrating Cloud Services.
NOTE: It is recommended to create a repository by forking a sample repository.
To add a Blueprints Repository to your space:
- In BitBucket or GitHub, create a repository. Copy the repository's URL.
- In CloudShell Colony perform the following steps:
- Open the Settings page.
- Click the Blueprints Repository tab.
- Click +Add a Repository.
- Click the required source control tool and paste the copied URL in the Enter your repository's URL field.
- Click Connect.
- Authorize CloudShell Colony's access to your GitHub repository.
Your blueprints repository is now set up.