-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time to swap off Cloudinary #644
Comments
Heyo! I'm not an expert on eleventy_img, but I did contribute a bit to it. Please feel free to tag me if you need help with anything related. Something like a cron job (or maybe github actions or netlify functions?) that takes a screenshot would work quite nicely imo. The files processed by eleventy_img have a hash in them, calculated from the original file's content (unless the original file is a URL). Because the hash necessarily changes when you change the original screenshot, you can cache them indefinitely in the browser with I also wrote a plugin to cache images across builds on netlify: https://github.com/zeroby0/netlify-plugin-11ty/ |
@xdesro This netlify function should be hosted as a separate project to decouple its cache from https://personalsit.es. I made my own project to handle screenshots and deployed it to netlify, but you can fork it and deploy it by yourself if you want. More info about 11ty/api-screenshot: https://www.zachleat.com/web/screenshots/ |
This is exactly the reason, @woodrunsdeep :D. Cloudinary killed my plan and I haven't merged in @kirillunlimited's PR just yet. Thanks for the heads up! |
We've exceeded the free tier of Cloudinary lol. I think something like @11ty/eleventy-img will serve this need better. Not sure how to handle caching and re-requesting screenshots. Right now, if someone updates their site, I can just delete the image on Cloudinary and the app knows to re-screenshot.
The text was updated successfully, but these errors were encountered: