Easy switch to maintenance page #350

New Issue

Closed

opened 2022-10-17 17:21:44 +02:00 by muppeth · 3 comments

muppeth commented

2022-10-17 17:21:44 +02:00

Owner

We used to use ansible to switch template to maintenance when we wanted a service to not be accessible. This works well for cases where service is planned to be in maintenance mode for long time.

However we should have an easy way to load site in maintenance without the need for PR/approval process.

We used to use ansible to switch template to maintenance when we wanted a service to not be accessible. This works well for cases where service is planned to be in maintenance mode for long time. However we should have an easy way to load site in maintenance without the need for PR/approval process.

muppeth commented

2022-10-17 17:28:46 +02:00

Author

Owner

I can think of two ways:

Use ansible role as is and add in host_vars extra vhosts (eg. gitea.maintenance) that arent enabled but have all the info such as root pointing to general maintenance page, having all needed certificates etc).
Add task to nginx that will deploy maintenance vhost (eg. gitea.maintenance) as above, if item.maintenance: 'true' for vhost is set.

If we need to switch service to maintenance mode, we just need to remove the current link to sites-enabled and create new link linking to gitea.maintenance vhost. When maintnenance mode is not needed, we either run playbook on proxy servers or change the link back.

Option 1. adds more vhosts in host_vars but doesnt touch the role while the option 2. requires just extra attribute to host_vars but requires extra task on the role.

I can think of two ways: 1. Use ansible role as is and add in host_vars extra vhosts (eg. gitea.maintenance) that arent enabled but have all the info such as root pointing to general maintenance page, having all needed certificates etc). 2. Add task to nginx that will deploy maintenance vhost (eg. gitea.maintenance) as above, if `item.maintenance: 'true'` for vhost is set. If we need to switch service to maintenance mode, we just need to remove the current link to `sites-enabled` and create new link linking to `gitea.maintenance` vhost. When maintnenance mode is not needed, we either run playbook on proxy servers or change the link back. Option 1. adds more vhosts in host_vars but doesnt touch the role while the option 2. requires just extra attribute to host_vars but requires extra task on the role.