notrab

send me an email jamie @

if anyone reading this would like access to S3, i can get you added.

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.

Agreed, it looks pretty nice!

Sinatra is beautiful!

Yay PHP! Let me know how you get on

Thanks Campak!

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.

Is FuelPHP or CodeIgniter still going? Those were my two favourites back in the day before Laravel came on the scene.

Appreciate the feedback, I'll work on it. I have lots to learn it seems!

I think it looks cute

Thanks!

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.

That looks awesome!

Hono is to credit for the design, really nice!

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.

This `@live` directive implementation uses server-sent events to send messages to the client with any changes that happen on the server in the format of https://jsonpatch.com

This means users don't need to poll to fetch all the data again but only get the data that changes. Poll2Hook looks great though, certainly a great solution if the service you're using doesn't have something native built-in.

The purpose of the `@live` query is that it uses server-sent events to update the client state with any new changes that happen on the server. It's correct that you can use something like Tanstack Query, useSWR, React Apollo, or even fetch to poll the server again but that requires fetching all of the data that was previously fetched to update the client state. Instead with SSE, you get a diff in the format of JSON Patch that you can use to apply any changes to the current state without refetching everything.

There are many implementations of Live Queries (some that just use polling under the hood) but we really like the concept of using JSON Patch with SSE.

Full disclaimer: I've been working with Grafbase on some content lately, but I thought I'd drop my 2c.

Over the years I've spent a bunch of time working with GraphQL services such as Graphcool, Hasura, Prisma Cloud (their old version), AppSync, StepZen, and many others.

While we've moved on a lot since the days of what Graphcool gave us in the early days, the DX of most of these newer services still lacks what you get with the likes of Vercel and their local development experience.

Grafbase are working on this now with their CLI, and wow, it's really interesting to see bringing the full serverless experience to your local development environment. I can build my app locally, without Docker, or any configuration outside of my SDL and get locally what I get in production.

Grafbase has a bright future!

Congrats on the announcement, and name change.

Considering the shift over the last decade to microservice APIs (including GraphQL here), we're now seeing a shift in lots of companies moving to become the gateway/orchestration layer. So it makes sense you guys move into this space. You've already caching, analytics, monitoring, etc. Now these services exist for all subgraphs!

I wish you guys the best of luck! As said in another comment, stellar team to make it happen.

PS. What would be interesting to see is some kind of "control plane" movement with Stellate. Give me a binary I can run that you generate based on all of my config.