What is the best way to implement an image CDN, Cloudinary in my case?
I was going to use the URL API, and append image()->url() to the cloudinary URL for an automatic upload and serving, but I saw that we can code a thumb driver.
Wich way is the best? what are the downside to the 1st method? (As I have no idea how to develop a thumb driver, i’m more inclined to go the simple way but don’t know if it’s a good idea). Is any of you develop their own thumbnail driver and can give me an example?
How exactly do you want to use cloudinary? Just for thumbnail generation with the user still uploading images to pages like before via the Panel? Or without the Kirby backend?
I want to serve all my portfolio images (and thumbnails) via cloudinary. i think i’ll go by the URL API method as i can’t understand the thumb drive and I’ve no idea where to start (i’m not a developper).
If I understand correctly, cloudinary can handle image appending the original url to the cloudinary url, and manage it just with that, maybe it’s the best way for me.
I used the fetch URL method for now, it uploads images directly in cloudinary (you have to uncheck the fetching security in your account and limit fetching from your domain). It works well.
cloudinaryfetchurl is a variable in my site.txt with the URL given by Cloudinary and if it’s empty, I fallback on native thumbnails. I cold push further and turn cloudinary parameters into variables, and create a custom kirby tag, or even factorize a little bit, but for now it’s enough for my use.