-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Automatically set Pretix to maintenance mode #487
Comments
I agree with that this feature is required I studied your current ansible configs for the maintenance things, and I think automating this can be simple. Setting up pretix involves installing all relevant files - also the maintenance html and nginx config. If I understand correctly, we can then toggle the maintenance mode by simply replacing the nginx file in the We can thus create a periodic timer which triggers a systemd service, which simply replaces the symlink and reloads nginx. |
Oh that seems better than the way I do it currently. Then we can remove some Do you have the time to implement this? |
You do Wilford, I do this 🫡 |
I assume the given times must be compared to UTC time and not local time? If so, are the given times already UTC offset (aka should they be 2100 and 0400 iirc)? |
The times I specified are UTC. This way, no matter what timezone Pretix and Mollie use (I.e., CET or CEST), it will never mess up. |
Due to Mollie and Pretix's report cut-off (and Mollie's payment) cutoff being slightly different, this can lead to some headaches for the treasurer when booking in the sales, as the sale can be in week 1 for Mollie, but in week 2 for Pretix, leading to some annoying digging every so often. This only occurs in the night from Sunday to Monday.
Since Pretix now has a new maintenance mode, I'd like Pretix to be in said mode between Sunday 22:00 and Monday 05:00 every week.
@SilasPeters you're much more familiar with Ansible than I am, what would be the best way to perform this? I could imagine a local copy of sadserver on sadserver, and a cronjob which flips the variable on Sunday evening and deploys, and one which does just the opposite on Monday morning. Though I'm sure there is a prettier way to accomplish that.
The text was updated successfully, but these errors were encountered: