Reenable staging deployment with trigger
Description / Overview
A staging deployment that is as close to production possible would be useful. We could use it ourselves to validate that the current master works as intended and could also use it to provide other people access to a safe test instance where they can play around with the application.
Because at some point all submissions might be corrected, we could add a ci trigger that causes the staging database to be reset. This trigger could be called by a cron job running on the staging server.
Use cases
- Validate current build by manually checking
- Provide access to safe test instance for people interested in the application
- This could also be used to provide tutors a way to look/play with the app before correction
Links / references
Feature checklist
(Make sure these are completed before closing the issue, with a link to the relevant commit.)