Environments are used to help facilitate our workflow for code/files/databases.
We utilize a 3 environment workflow to support our CFW.
Development: The development environment is the first line of defense against bugs. Here, we deploy code and configuration changes to test any newly implemented features of bug fixes. Any issues found are dealt with before re-deploying for further testing. The process is iterated until the code is ready for the next stage of testing.
Staging: Once satisfied with our 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: Once the code has been thoroughly tested, it is then pushed to production where it is made “live” to the world.
Refreshing:
From time-to-time, we need 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 production.
This means any content or configuration created in the stage/dev environments will be lost.
Note: Moving things between environments is only done by the ITS web team.
Add Comment