I just read this post:
And I wanted to add a question there, but the post was already closed. I wondered if there is anything I could improve in the following setup regarding using netlify’s cache, or if that is already handled.
We have a headless WordPress installation, that is used with vue.js and nuxt.js.
We built a custom fetcher that, on each build, first fetches the data from the WP REST API, saves it into .json files and then generates all the static html files for each post/page.
In the post above it is mentioned that for files that are not reuploaded the cache would be used.
But in our case those files are created during the build.
Is there a way to mark to netlify which of these files have been unchanged?
Normally maybe just a handful of posts have a content that has changed and hundreds of other posts are exactly the same and will result in the same generated .html files.
I know that this setup is a bit different from what is described in the post, but I face the issue that the post processing is taking quite some time (although I almost shut it off completely) and I assume it is because netlify is scanning all the new files, although they are probably exactly the same as the 10 deploys before…
Thanks in advance on any inputs.
Completely different approaches to this problem are of course as well appreciated.