Jamie from bunny.net here. Apologies for the delay after announcing S3. Building this required deeper changes to our storage foundation than initially anticipated, while ensuring that existing storage customers remained unaffected.
For clarity, S3 compatibility for Bunny Storage is now live in closed preview (since Jan 2026) with a select set of users.
We’ll soon introduce a sign-up page where users can register their interest, and in the next phase we’ll grant access to invited users.
turso deprecated their edge replica offering when they went all-in on rewriting sqlite so bunny fills a nice void here. while turso didn't pull the plug for existing customers, new customers were left looking for alternatives with edge replica (that couldn't replicate on-device), and bunny does a nice job here.
turso also made it so your primary had to be in one location, but bunny will move it around based on latency on next boot.
S3 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.
True true. I went back and forth so much in the early days of CodeIgniter, Rails, Fuel and Cake.
Eventually discovered just building stuff was going to bring me the most joy, no matter the tool. It's been a joy learning PHP again though, even if I do suck at it right now.
1) When I started this, I thought could this be an HTMX-PHP framework. If you see the examples directory, I added a few HTMX examples early days. Maybe I can niche down on this...
2) If I'm honest, I don't know yet. I first started building the router, then I was told through some feedback that there's been a lot of research (rightly so) into this area and I would be better off implementing the FastRouter that's in Slim, so I switched to that...
As mentioned above, if I could make this framework fit with HTMX more, I could have a PHP framework that talks HTMX with less of the wiring up. I still need to figure this out.
3) I've avoided building an official site/docs for it, but I might have to. I had hoped the examples were a good source, but as more features were added, creating official docs site might have to be my next task.
PHP isn't yet part of my default stack, but I am trying to thanks to what I've been learning building Dumbo.
100% like every other framework. I'm primarily a JS dev, so it's in my nature to create yet another framework...
But seriously, this has been a tool for me to relearn PHP, and those contributing so far have also been learning PHP. If it ends up just bein (and nothing more than) something helps me, as well as others learn more about PHP, it's a success.
I guess that's still to figure out... it's mostly been an experiment to relearn PHP... I guess keeping a similar DX to Hono's context->X is where I was coming from originally.
I was researching effective ways to advertise the dropshipping store I had created on Shopify, I stumbled upon the fact that an old colleague was actually working on this Order Legend tool. Paying a 12% fee for orders I wouldn't have acquired otherwise seems like a fair price.
I should add that using regular queries with Apollo, URQL, etc. is perfectly fine. If you're building an app that requires realtime data then `@live` queries can be really useful. The data can update in realtime without refreshing and there's no need for WebSockets!
There are limitations to server-sent events, but `@live` queries is a perfect fit imo.