Environments

Cloudstation environments provide isolated instances of all services within a project, ensuring that changes can be tested and iterated upon without affecting the production environment.

How it Works

By default, all projects in Cloudstation are created with a production environment. Once a project is established, additional environments can be created and configured to support various stages of development and testing.

Use Cases

Environments are essential for isolating changes from the production environment, allowing for safe iteration and testing before deployment.

  • Create development environments for each team member that mirror the production environment, ensuring consistency and reducing integration issues.
  • Set up separate staging and production environments that automatically deploy changes from different branches in your code repository, facilitating continuous integration and delivery.

Tips for Managing Environments

  • Consistent Configuration: Ensure that all environments are configured consistently to avoid discrepancies during deployment.
  • Automated Testing: Implement automated testing in non-production environments to catch issues early.
  • Resource Management: Monitor resource usage in each environment to optimize performance and cost.
  • Access Control: Restrict access to production environments to minimize the risk of accidental changes.

Support

Explore the Environments guide for more detailed information on how to create, use, and manage environments effectively.


Edit this file on GitHub