@zachleat @Netlify I’ve also been noodling on the idea of generating an .eleventyignore file automatically based on what is found in the build cache since it has a handy list method.
https://github.com/netlify/build/blob/master/packages/cache-utils/README.md#list
Some reverse engineering required to figure what source file made what permalink.
https://github.com/netlify/build/blob/master/packages/cache-utils/README.md#list
Some reverse engineering required to figure what source file made what permalink.
@stefanjudis @Netlify They are so much fun!
I've been experimenting with them quite a bit over the last couple of weeks. I'll write up my process soon, but until then, @Tzmanics is dropping knowledge all over the place!
🧠 👉 https://www.netlify.com/blog/2020/04/30/whats-a-netlify-build-plugin-series-part-1-using-build-plugins/?utm_source=twitter&utm_medium=using-build-plugins-tzm&utm_campaign=devex
I've been experimenting with them quite a bit over the last couple of weeks. I'll write up my process soon, but until then, @Tzmanics is dropping knowledge all over the place!
🧠 👉 https://www.netlify.com/blog/2020/04/30/whats-a-netlify-build-plugin-series-part-1-using-build-plugins/?utm_source=twitter&utm_medium=using-build-plugins-tzm&utm_campaign=devex
For example, I used this to enable incremental builds on one of my projects.
https://twitter.com/philhawksworth/status/1256293798969212933
https://twitter.com/philhawksworth/status/1256293798969212933
Currently having fun with @Netlify Build Plugins!
🚀 https://www.netlify.com/build/plugins-beta/?utm_source=twitter&utm_medium=cache-utils-pnh&utm_campaign=devex
Getting access to the cache between build offers some great opportunities!
🚀 https://www.netlify.com/build/plugins-beta/?utm_source=twitter&utm_medium=cache-utils-pnh&utm_campaign=devex
Getting access to the cache between build offers some great opportunities!
Kudos to @timbray for showing that he has the courage of his convictions.
https://www.tbray.org/ongoing/When/202x/2020/04/29/Leaving-Amazon
https://www.tbray.org/ongoing/When/202x/2020/04/29/Leaving-Amazon
@jamiemchale @Netlify Yeah... I had good success on Friday with incremental builds in an example site I made with @eleven_ty. Thanks to the new access to @Netlify's build cache, you can make this work nicely.
https://twitter.com/philhawksworth/status/1256293798969212933
https://twitter.com/philhawksworth/status/1256293798969212933
@richardherbert Yeah! He was one of my absolute favourites during that era. Utter legend!
@jamiemchale @Netlify I suppose that in addition to how often the content might change for each user, it depends somewhat on how many users you might need to service this way.
@jamiemchale @Netlify So, 1 role per user? Sounds like that would mean pages are unique for each user, which is a good use case for authentication/authorisation on the API which populates pages rather than unique pages. A popular pattern and what we do for http://app.netlify.com.