Cache posts

[nilsnolde]

To avoid requesting the post from any platform even if nothing has changed since the last pull, the plugin should cache the posts. Use a HEAD request for this.

The logic to cache the post could be:

• cache HTML from Github
• name pattern for post: owner/org|repo|postname|datestring (or find a delimiter which can't be part of the resource URL)
• if no file like that present, pull the post, convert raw file to HTML, cache HTML following name pattern
• if file present:
  • issue HEAD request to the file's API location
  • extract datestring from cached file name
  • if last-modified response header is newer than extracted date string:
  • re-fetch the file contents from Git
  • convert to HTML
  • save new cache file, delete old one
  • display contents of cached file

[nilsnolde]

Update: Gitlab doesn't send a last-modified header :roll_eyes: or anything related. So maybe the only option here would be to ask for the last commit and take the date out of there. A tiny little bit slower than for other providers, but still okish..

[eblabs]

Hi @nilsnolde , thanks again for your help.

About the caching, checking the document edits sounds like a great idea. Although as an intermediate step, would this simpler approach be possible?

• When a page is requested, save the cache and store the timestamp.
• Then when another view is requested, based on an "expiry time", either display the cache is displayed if its still "fresh", or its renewed if the timestamp is expired.
• The expiry time could be minutes or hours depending on the config json file.

Maybe this is something you're already doing.

Thanks!!

[nilsnolde]

Not even that much simpler I guess. Requesting a HEAD is not the more complicated thing to do IMO.

I think most of the work is researching how to best cache in WP, i.e. which directory to put them in or how (if) to flag that as cache, so it survives plugin & WP updates. Granted, that's not more than an hour. The rest is pretty straight-forward. I'd expect a day for this approx.

I'll take a look into this in a while, 1-2 months max. I don't consider it critical for most blogs. Can of course be sponsored money-wise, then I'd find time quicker;)

[eblabs]

Thanks @nilsnolde, sure I'd be happy to pitch in $$. Do you have a donation link or anything?

btw, I found a wordpress plugin that had a caching system that seemed to work well, it might be worth looking into for ideas. https://github.com/anytizer/hosted-content-importer.wp

[nilsnolde]

Yeah and there you got me.. I should set up smth like a donation link for us before slinging around things like that :wink: Thanks for the offer and the link. I'll dig in when I find the time.

[nilsnolde]

Quick shoutout @eblabs: #19 and @danilopinotti will implement static caching, merging and releasing soon. Wanted to let you know already, I'm kinda excited about this :smile: And sorry for the long wait

[nilsnolde]

Merged and v1.1.0 released to plugin repo :champagne:

[eblabs]

Thanks so much for the update @nilsnolde !! Really appreciate all your effort on this super handy plugin 👍