4 ms·
Pretty cool. I’ve been using Bunny as a Cloudflare replacement for a couple of years and my experience has been flawless.
by pier25 9mo ago
Pretty cool. I’ve been using Bunny as a Cloudflare replacement for a couple of years and my experience has been flawless.
- jsheard 9mo agoIt does feel like they're spreading their resources pretty thin though, the S3-compatible interface for their file storage has been "coming soon" since 2022.
- kilroy123 9mo agoI, too, have the same worry.
- pier25 9mo agoYeah that's true. The lack of S3 compat hasn't been an issue for me personally but it would be nice to have it for their edge storage.
- pousada 9mo agoThat’s the problem with keeping a public roadmap - in the end everyone is unhappy and also not really more informed
- notrab 9mo agoS3 is currently in closed preview with some users. It's quite easy to get added for those keen to try it. More using it and providing feedback, the quicker it'll become public preview.
- cobertos 9mo agoHuh, 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 9mo agoThey 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 9mo agoYou 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)
- cuu508 9mo ago> don't use CNAME flattening with DNS-routed CDNs like Bunny though What is the problem with doing that?
- deleted 9mo ago[deleted]
- osener 9mo agoWhen 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?