-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
export HTML schedule on schedule release & intervals #277
Comments
There is no good way to catch bulk updates, but we don't really do those. Instead on updating on talk changes directly, how about storing a dirty flag that will be reset once the schedule has been regenerated? |
The HTML export also needs to be regenerated when the organiser uploads a changed CSS or logo. |
We now have a good way to do this! event.cache.set('rebuild_schedule_export', True, None) will have to be added when
|
I decided that it doesn't hurt to be careful, so this flag is set on any submission save and speaker save, currently (as long as the schedule is configured to be exported on release). I think it would be way harder to make sure a change does/does not affect the schedule than to just trigger a regeneration of the schedule export periodically. I've limited the automatic regeneration to 30 minutes to be on the safe side in terms of DoS. |
Static schedule exports can currently only be triggered manually via a management command. But we know when the data changes so looking at #275 we should do that automatically, if the user wishes us to do so.
The text was updated successfully, but these errors were encountered: