Environments

Environments are used to help facilitate the workflow for code, files, and databases.

Environments Workflow

The Common Framework is supported by a three environment workflow:

• Development (dev): The development environment is the first line of defense against bugs. Here, we deploy code and configuration changes and test any newly implemented features or bug fixes. Any issues found are dealt with before re-deploying for further testing. This is an iterative process until the code is ready for the next stage of testing.

• Staging (stage): Once satisfied with code and configuration, and consider it fairly stable, it is then deployed to the staging environment for further testing. This is where Quality Assurance (QA) is performed. This is where we involve college teams to access the staging servers and ensure that the application works as it should.

• Production (prod): Once the code has been thoroughly tested, it is then pushed to production where it is made “live” to the world.

Refreshing Environments

From time-to-time, the District Web Team needs to refresh the stage and dev environments to ensure when we /you are testing against fairly current copy of data (content created on prod). This entails replacing the stage/dev database and file with the ones from prod.