Cloud Environments

SimpleReport is spread across multiple environments for the purposes of development, testing, demonstration, and production purposes. Some are deployed to automatically as part of our pipeline when code is merged to main, while others require manual updates and are considered "volatile".

Development Environments

Name:

• dev
• dev2
• dev3
• dev4

Update Strategy: These environments are updated on-demand with GitHub Actions. They should not be relied upon to be in sync with main.

Intended Use: Developers should use these environments to test enhancements and bug fixes, and to verify deployment behavior in a cloud environment. This environment's data is volatile, and should not be relied upon for feature testing or demonstration.

Testing Environments

Name: test

Update Strategy: This environment is automatically updated on a push to main.

Intended Use: Used for automated end-to-end and load testing. This environment's data is volatile, and should not be relied upon for feature testing or demonstration.

Name: pentest

Update Strategy: This environment is updated on-demand with GitHub Actions. It should not be relied upon to be in sync with main.

Intended Use: Used for security and penetration testing, including by automated toolsets. To facilitate testing, alerting is disabled in this environment. This environment's data is volatile, and should not be relied upon for feature testing or demonstration.

Training/Demonstration Environments

Name: training

Update Strategy: This environment is automatically updated on a push to main, contingent on a successful automated deployment to stg.

Intended Use: Used externally by potential and onboarding users to get a better understanding of the product. This environment's data is ephemeral; the database is wiped and re-seeded every 24 hours.

Name: demo

Update Strategy: This environment is automatically updated on a push to main, contingent on a successful automated deployment to stg.

Intended Use: Used externally by product managers, support staff, and other personnel to demonstrate the production version of the application to potential end users.

Pre-Production Environments

Name: stg

Update Strategy: This environment is automatically updated on a push to main.

Intended Use Used as a validation gate for code, deployment, and infrastructure changes on a prod-like environment before new code from main is rolled to active demonstration/production environments. A failure to deploy to stg blocks deployments downstream to demo, training, and prod.

Production Environments

Name: prod

Update Strategy: This environment is automatically updated on a push to main, contingent on a successful automated deployment to stg.

Intended Use: Used for live data collection and processing by end users. This is the SimpleReport.