Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by aarondf on Friday February 11, 2022 @07:42AM
(#30300739)
Where are the images stored in a setup like this?
[ Parent
| on HN ]
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by aeyes on Friday February 11, 2022 @08:12AM
(#30301022)
You could use Cloudflare R2 if you already are on Cloudflare.
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by samhw on Friday February 11, 2022 @08:21AM
(#30301128)
R2 doesn't exist yet: https://www.cloudflare.com/en-gb/r2-storage/ (And, more importantly, it's not very clear when it will exist.)
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by jgrahamc on Friday February 11, 2022 @09:12AM
(#30301677)
From the earnings call yesterday: "We're on track for R2 to progress to open beta in Q2 and then be generally available in the second half of 2022."
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by samhw on Friday February 11, 2022 @11:15AM
(#30303134)
Oh, nice! Thanks for that tidbit, appreciate it :)
Edit: I'm an idiot, you work for Cloudflare, lol - I thought you were just particularly sharp-eyed
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by celicaraptor on Friday February 11, 2022 @08:39AM
(#30301316)
You can use Backblaze B2 with Cloudflare in front in the mean time.
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by dgb23 on Friday February 11, 2022 @10:51AM
(#30302809)
R2 is something I look forward to.
I'm just imagining what would happen when would also provide managed Postgres in the same easy to handle and affordable manner as their other services.
Re:Migrating from Netlify to Cloudflare Workers Sites for 2x...
by samhw on Friday February 11, 2022 @11:17AM
(#30303175)
For sure: Cloudflare is increasingly feeling like a better alternative to the 'bare cloud' providers, for most of my projects and I suspect also for the 99% of companies who are just building generic CRUD web/mobile app backends.
Customisability is AWS/GCP's strong suit, but as a corollary they don't make it nearly as easy to 'paint within the lines' - which is an odd UX stance to take when, by definition, 99% of your customers fall within the 99%. Personally I would have designed it to be 'simple by default, configurable if you need it', but far be it from me to say what's best.