Not sure if anything has been implemented yet, but my thoughts:
Simple method - cron job that runs site-generator --all every 6 hours
More complex - Update individual pages. Need to define what triggers the update and what is updated
New day will publish the latest episode which affects the following pages:
index
correspondent
correspondents (if a new correspondent)
episode -- both current episode and previous episode
episodes
tags
series (if part of a series)
series_episode (if part of a series)
RSS feeds once they are statically generated
New comment on an episode
episode
index (if episode is within the Latest Episodes time frame)
New show
index (update if days until show could be released is within time frame)
RSS feeds that contain future episodes once they are statically generated
Others I may not have contemplated.
I envision an update tool that is run either manually or periodically that queries the database and generates a list of pages that need updated in the form of
the site-generator arguments and then runs the site-generator with them.
Not sure if anything has been implemented yet, but my thoughts:
Simple method - cron job that runs ```site-generator --all``` every 6 hours
More complex - Update individual pages. Need to define what triggers the update and what is updated
- New day will publish the latest episode which affects the following pages:
* index
* correspondent
* correspondents (if a new correspondent)
* episode -- both current episode and previous episode
* episodes
* tags
* series (if part of a series)
* series_episode (if part of a series)
* RSS feeds once they are statically generated
- New comment on an episode
* episode
* index (if episode is within the Latest Episodes time frame)
- New show
* index (update if days until show could be released is within time frame)
* RSS feeds that contain future episodes once they are statically generated
Others I may not have contemplated.
I envision an update tool that is run either manually or periodically that queries the database and generates a list of pages that need updated in the form of
the site-generator arguments and then runs the site-generator with them.
I am currently running a job that updates the code, downloads the db, and then does a update all every 3 hours.
It's working OK but once an hour might be better so that comments get updated sooner.
I am currently running a job that updates the code, downloads the db, and then does a update all every 3 hours.
It's working OK but once an hour might be better so that comments get updated sooner.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The static pages need to be generated at least every six hours, or as soon as substantial changes have been made to the site.
Not sure if anything has been implemented yet, but my thoughts:
Simple method - cron job that runs
site-generator --allevery 6 hoursMore complex - Update individual pages. Need to define what triggers the update and what is updated
Others I may not have contemplated.
I envision an update tool that is run either manually or periodically that queries the database and generates a list of pages that need updated in the form of
the site-generator arguments and then runs the site-generator with them.
I am currently running a job that updates the code, downloads the db, and then does a update all every 3 hours.
It's working OK but once an hour might be better so that comments get updated sooner.