...
Keep your session open because you will use the automation scripts to send the release notification at the end.
Deploy
...
to
...
DR Web
Normally, we deploy to SF first, but since we want to verify that DR is working before deploying in SF, today we will deploy to DR first by running the following in DR PROD WEB:
| Code Block |
|---|
cd /var/www/html sudo ./deploy_eas_init.sh 105b3579cb3d a192794562a3 samuelvaldez |
Test the application to make sure everything works.
...
If testing in SF passes, deploy the web app to DR PROD with steps parallel to SF PROD (WEB only).
Make sure the DR web application works.
You will not be able to log into the web application in DR if DB replication is running.Put DR PROD WEB server into STANDBY mode
Deploy App to Web (SF)
If all goes well with the DR deployment, log into SF PROD WEB and deploy the application using the same commands as in DR.
Test the application to make sure everything works.
Test DR and put app in standby mode
Quickly ensure that data from above test is reflected in DR web app and then put the application into standby mode by running the following:
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_DR |
...