...
5 - Deploy the Web Application (SF)
- Deploy the Web application to SF PROD WEB per the instructions that are on * * WEB Server. If you staged the uncompressed repositories ahead of time, then you can use these commands to deploy the Web application:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html sudo ./deploy_eas_init.sh e7696197ffe0 91ac3c3c21bf samuelvaldez |
- Test the application to make sure everything works.
...
| Note | ||
|---|---|---|
| ||
You will not be able to log into the Web application in the disaster recovery production environment (DR PROD WEB) if database replication is running. |
- If testing in the San Francisco production environment (SF PROD *) is successful, then deploy the Web application to the disaster recovery production environment (DR PROD *) with steps that parallel those that were performed in the San Francisco production environment (* PROD WEB only).
- Make sure that the disaster recovery production environment Web application functions correctly.
- Testing the disaster recovery production environment Web application surfaced this issue: DR PROD WEB/GEO cannot connect to DR PROD DB
- Place the disaster recovery Web server (DR PROD WEB) into standby mode:
...
7 - Release Notifications
- Remove 1.3.8 from the road map.
- Publish the blog post for this release. Ideally, this blog post would have already been drafted. An example is Release 1.3.6.
- Log on to the automation machine (SF PROD AUTO) and run the following job to send the release announcement to stake holders:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd C:\apps\eas_automation\automation\src python job.py --action EXECUTE --job announce_new_release --env SF_PROD |
...
- This release announcement will also be sent to the Yammer All Company group, so check your email inbox for the request from Yammer to post the release announcement there.
- Return to Step 26 of the release checklist because you are all done here!
...