[cobertos]

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

[pier25]

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.

[jsheard]

You can also create a standalone pull zone and point your existing DNS provider to the CNAME they give you.

(don't use CNAME flattening with DNS-routed CDNs like Bunny though, if you must use an apex domain then use the CDNs integrated nameservers)

[osener]

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?

[Daegalus]

I have been using them for over a year. THey have the same flow as Cloudflare, point domain to thier CDN, set CDN Pull Zone to target your server. I havent had to do anything.

They even support websockets.

Why they cant do is the TUnnel stuff, or at least fake it. I have ipv6 servers, and I can't have the IPv4 Bunny traffic go to the ipv6 only sources.

[victorbjorklund]

Amazing. I had not noticed they support websockets now. That was always what I missed from CF.

[victorbjorklund]

It should work as a drop in. You can just proxy your website. You don’t need to upload anything to Bunny (but you can if you want).