Put Crowdbreaks under maintenance
Closed this issue · 5 comments
- Put Heroku on maintenance
- Put AWS service (EC2s, lambdas, …) on sleep mode
- Maintenance page has been created and uploaded to S3: https://crowdbreaks-static-pages.s3.eu-central-1.amazonaws.com/errors/maintenance.html
- The
MAINTENANCE_PAGE_URLENV variable has been set on both staging and production - Staging is now in maintenance mode (but resources are still up)
Waiting for @lauespinosa ok before putting the app in maintenance.
See https://digitalepidemiology.slack.com/archives/C37BXFDK2/p1683888541232439
Laura Espinosa Montalban
12:49 PM
After discussing with Marcel, there are some aspects that are still relevant for the current article I am working on and potentially the remaining work of my PhD. It was taking me too much time trying to collect all this info and data. Marcel suggested to put in maintenance only the public website and leave the website for admins still running.
@marcel.salathe, please jump in if I understood it wrong
Hi @lauespinosa !
I hope you’re doing well. I’ve deployed some changes to crowdbreaks staging, removing public access (routing to a maintenance page instead) while keeping the admin access.
Could you check it out and see if you have everything you need there before I deploy it to production?
You can still sign in by directly following https://crowdbreaks-stg.herokuapp.com/en/users/sign_in
If you encounter a basic auth sign form the username/password to pass it is the crowbreaks vault on 1Password (crowdbreaks-stg.herokuapp.com). Let me know if you encounter any issues.
Thanks!
Hi @yannis ,
Thank you, you can deploy to production, I can see everything I need