Drupal Enterprise 9: Managing Multiple Environments
Your Drupal site will consist of three environments:
- A development (or 'dev') environment with a URL of site.dev.umn.edu
- A staging (or 'stage') environment with a URL of site.stg.umn.edu
- A production (or 'prod') environment with a URL of site.umn.edu
This site is usually used for developing code such as sub-themes or custom modules. This is the environment where the developer will upload, de-bug, and troubleshoot code. This can also be used to test content or configuration before it is implemented on the live production site.
This environment is subject to being overwritten without notice and should not be used as part of your standard development process.
The staging environment is primarily used for OIT testing code updates against production-like databases. This environment uses the latest development version of the platform code as developed by the OIT Drupal Team. The site code on this environment is pointed to the production site code regardless of the referenced stage branch listed in Drupal Management (authentication required)
When the Drupal Team sends out a communication that there is an upcoming update, you can test it in this environment.
This is the public facing site where people go to consume your content. This is also where the contributors add content to the site.
Moving code between environments
You may need to copy the site from one environment to another. An example would be adding a theme update after a site has been launched.
Changes should be tested in the development environment. To test code in dev, use Drupal Management to copy your production database to the development environment and deploy your code.
You can request updates to your production environment by submitting a request with the Drupal Support Team.