Landing page content seems to take a while to update

[lostintangent]

After creating a new GistLog and/or changing an existing GistLog's published status (via the gistlog.yml file), it seems to take a while for the change to take effect on my landing page. Is there an expected delay between publishing new logs and when they should appear on the landing page? Ideally, a user could change the published state and have it take effect immediately, in case they accidentally published something they wasn't ready/etc.

If I open the Gist page directly (e.g. https://gistlog.co/{user}/{id}), the content is always fresh. So it simply seems to be an issue with the landing page (e.g. https://gistlog.co/{user}). I noticed some caching being done in the landing page client, but I couldn't tell how long the cache duration was. Thanks again for making an awesome product!

[mattstauffer]

Good eye! I think it's 10 minutes cache right now; it's mainly just because we're both rate limited on our calls to GitHub, and those calls can be kind of slow.

Let me try to think of any way we could bypass that.

One option I thought of was having a panel you can visit when you're logged into Gistlog as your GitHub user that allows you to do a few small things like reset that cache early in that scenario. I'm also open to other ideas from you or anyone else.

Thanks so much for your ideas!

[lostintangent]

Maybe you could provide an API to invalidate the cache for a specific user, and GistPad (or other clients) could call that whenever a new post is made and/or a post is changed for published to unpublished? That would be an easy change from my end, and the developer wouldn’t need to do anything manually to make this work as expected.