Special Deployment

Procedure for Special Deployment
August 28, 2017

Following are the steps required for this deployment:

Back up the production database
Create a new database on webcms to hold 'good content'. Grant Drupal's user all permissions on this new database (you can find this user's information in /var/www/html/sites/default/local.db.inc.) Import the copy of ‘good content’ that was created on stagecms to this new database (so you don’t have to wait while webcms runs all the db updates; will save half an hour of having the site in maintenance mode)
Create an html 'maintenance mode' template and save it to webcms in /var/www/maintenance_mode
Create the directory /var/www/html/sites/default/files-private/smartling and set its permissions so that the web server user can write to it
Put the site into Drupal's maintenance mode
Make ‘good content’ the production db and ‘good users’ the ‘user_source’ db by changing /var/www/html/sites/default/local.db.inc
Run the user migration
Back up the production db (was ‘good content’ - now has both good content and good users)
Make backup of the .conf file in /etc/httpd/sites-available
Edit the .conf file, changing 'DocumentRoot /var/www/html' to read 'DocumentRoot /var/www/maintenance_mode'
Restart apache
Drop the production db
Create the production db again with the same name - ensure that whatever user Stackbuilder uses to authenticate exists and has the necessary permissions
Restore the backup from step 6
Change the redirect so that site traffic goes to /var/www/html instead of /var/www/maintenance_mode (moving the backup file from 14 to replace the edited copy from 15.)
Take the site out of Drupal maintenance mode
Create a new database on webcms server 'transaction_log_restore'
Import the database backup from line 6 to 'transaction_log_restore'
Export all rows in edb_transaction_log from 'transaction_log_restore' that are not present in 'good content' database
Import (via Postgres) those rows into edb_transaction_log table in production database