...
- notify all stake holders before the release.
- eas commit id: 105b3579cb3d
config commit id: a192794562a3
execute all steps in the SF ENVs first and test the application.
- if tests pass, then execute steps on DR ENVs.
- In the unlikely event that things go very badly, we switch over to the old application in DR.
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 |
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.
Web into MAINT Mode
put the web servers into maintenance mode (SF WEB, DR WEB)
...
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 |
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.
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.
...