Release script for deploying Cal State

[crisr15]

Summary

Cal State needs an easier way to deploy. We talked with them about creating a deploy script that runs as a cron job on the server and looks for new releases from their repo. They decided this was the approach they wanted to use.

Acceptance Criteria

• [ ] A script that can be run as a cron job that will be scheduled for every 5 minutes and ping for releases
• [ ] The latest release will deploy to production
• [ ] Pre releases will deploy to staging.

Testing instructions

This ticket is not end user testable. Move to client QA after code review. Client can review the script to provide us with feedback and once they are happy with the script this ticket can be closed.

Notes

have a cron job that runs every 5 minutes and then looks for releases. So the server pulls from github and downloads the version when it sees new releases.
Prod looks for release Test looks for pre-release How would you roll back Either cut a new release off an old sha or delete the release and it will grab the previous one.
Ir.0.0.1 for scholarworks Da.0.0.1 for Digital Archive

[crisr15]

This is not working and needs to be investigated and fixed.