Page Comparison

...

• Development (dev): The development environment is the first line of defense against bugs. Here, we those with the Developer or Webmaster role can deploy code and configuration changes and test any newly implemented features or bug fixes. Any issues found are should be dealt with before re-deploying for further testing. This is an iterative process until the code is ready for the next stage level 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 shouldIf the ITS Web Team makes a change, they may ask College web staff to test the changes on stage for their website.

• Production (prod): Once the code has been thoroughly tested, it is then pushed to production where it is made “live” to the world. This is also where content creation and editing happens.

Code is always moved up the stack, starting in dev, then moving to stage, and then up to prod. Content is the opposite and should always be added in prod.

...

Keeping Environments

...

in Sync

It is important to keep the dev, stage, and prod environments in sync so that testing on one environment is the same as testing on another. To do this, 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 (regularly copies the content created on prod ). This entails replacing the stage/dev database and file with the ones from prod(databases and files) back down to dev and stage. These environment refreshes are a necessary part of ongoing site maintenance that is managed by the District Web Team.