*** THIS IS A DRAFT AND IS NOT COMPLETE ***
1 - Preamble
- eas changeset identifier: <eas-changeset-identifier>e7696197ffe0
- sfeas_config changeset identifier: <sfeas_config-changeset-identifier>91ac3c3c21bf
This deployment will consist of the following general steps:
...
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
|
# You should receive an email notifying you of the status of the backup.
# The database backup log file is another source of information about the
# outcome of the backups. Note that an empty database backup log file
# indicates that the backups were successful.
ls -la /var/tmp/dbbackup.log
cat /var/tmp/dbbackup.log
# The existence of the database backups can also be confirmed directly
# from the command line:
ls -la /mnt/backup/pg/daily/easproddb.sfgov.org-* |
...
- Deploy the automation scripts to SF PROD AUTO per the instructions in that are on * * AUTO Server. If you staged the compressed repositories ahead of time, then you can use these commands to deploy the automation scripts:
Code Block |
---|
language | bash |
---|
linenumbers | true |
---|
|
cd C:\apps\
python eas_automation_deploy.py eas_automation |
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 |
---|
language | bash |
---|
linenumbers | true |
---|
|
cd /var/www/html
sudo ./deploy_eas_init.sh <eas-changeset-id> <sfeas_config-changeset-id>e7696197ffe0 91ac3c3c21bf samuelvaldez |
- Test the application to make sure everything works.
...