zlacker

>>dabina+(OP)
Pretty cool. I’ve been using Bunny as a Cloudflare replacement for a couple of years and my experience has been flawless.

>>pier25+kg
Huh, how? Did you have to modify your site a lot to do switch?

I tried to test it out as a CDN replacement for Cloudflare but the workflow was a lot different. Instead of just using DNS to put it in front of another website and proxy the requests (the "orange cloud" button), I had to upload all the assets to Bunny and then rewrite the URLs in my app. Was kind of a pain

>>cobert+8u
They do have the CDN proxy too. Not sure when it was implemented though.

It's a similar process to Cloudflare. Point the NS to them and enable the proxy for a domain or subdomain.

>>pier25+Xy
When I tried it last year, their edge compute infra was just not there yet. It could not do any meaningful server-side rendering because of code size, compute and JS standard constraints.

Has this situation changed?

>>osener+hD
Depending on your precise requirements, I think it might have changed.

I've been trying out Bunny recently and it looks like a very viable replacement for most things I currently do with Cloudflare. This new database fills one of the major gaps.

Their edge scripting is based on Deno, and I think is pretty comparable to e.g. Vercel. They also have "magic containers", comparable to AWS ECS but (I think) much more convenient. It sounds from the docs like they run containers close to the edge, but I don't know if it's comparable to e.g. Lambda@Edge.