Skip to content
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

Closed
luto opened this issue Nov 19, 2017 · 4 comments
Closed

export HTML schedule on schedule release & intervals #277

luto opened this issue Nov 19, 2017 · 4 comments

Comments

@luto
Copy link
Member

@luto luto commented Nov 19, 2017

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.

  • generate export on schedule release #297
  • maybe generate in regular intervals
  • maybe generate on talk changes, e.g. the title changes: is there a way to catch bluk updates?
@luto luto mentioned this issue Nov 19, 2017
12 of 22 tasks complete
@rixx rixx added this to the 2017-12 milestone Dec 5, 2017
@luto luto mentioned this issue Dec 15, 2017
16 of 19 tasks complete
@rixx rixx removed this from the 2017-12 milestone Jan 7, 2018
@rixx

This comment has been minimized.

Copy link
Member

@rixx rixx commented Jan 21, 2018

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?

@rixx

This comment has been minimized.

Copy link
Member

@rixx rixx commented Nov 27, 2018

The HTML export also needs to be regenerated when the organiser uploads a changed CSS or logo.

@rixx

This comment has been minimized.

Copy link
Member

@rixx rixx commented May 17, 2019

We now have a good way to do this!

event.cache.set('rebuild_schedule_export', True, None)

will have to be added when

  • A talk is confirmed
  • A talk is unconfirmed
  • A talk changes in a visible way
  • A speaker changes in a visible way
  • Related data to a talk or a speaker (question answers!)
@rixx

This comment has been minimized.

Copy link
Member

@rixx rixx commented Nov 9, 2019

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.

@rixx rixx closed this in 20c647a Nov 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.