-
Notifications
You must be signed in to change notification settings - Fork 3
Scholar@UC Environment Deployment Procedure
Thomas Scherz edited this page Feb 18, 2021
·
9 revisions
- Create a tunnel: ssh [email protected] -L 2222:SERVER_NAME:22
- Deploy: cap dev deploy
- See https://git.uc.edu/UCLIBS/private_documentation/blob/master/Capistrano_Deploy.md for SERVER_NAME
- When the deployment is finished, check the log for errors.
- Visit https://scholar-dev.uc.edu to verify the site is up.
- Review Risk Matrix : https://github.com/uclibs/scholar_uc/issues/203
- When the deployment is finished, check the log for errors.
- Visit https://scholar-qa.uc.edu to verify the site is up.
- If a Security scan against QA is needed, set date for request of Security scan to be the date of deploy to QA.
- Visit Hailstorm and request scan: https://uc.teamdynamix.com/TDClient/Requests/ServiceDet?ID=5368
- If a Hailstorm scan will take place, await results and determine if remediation is necessary before moving on to Production server.
- Visit UCIT Change Request: https://webapps2.uc.edu/ucit/changemgmt/ChangeManagementForm.aspx
- Wait for request approval. Once approval has been received, communicate date and time to stake holders.
- When the deployment is finished, check the log for errors.
- Visit https://scholar.uc.edu to verify the site is up.