Live data from Hacker News

Pocketbase – open-source realtime back end in 1 file

pocketbase.io

131–140 of 211 posts

Re: Pocketbase – open-source realtime back end in 1 file

#131

Earlier quoted context omitted.

This was my exact comment, thanks. It is a very good piece of work, and extensible with JS (I just tried that). I have a fear about the future because the dev is alone, and responds alone in the discussions. He is also quite, how to say, "rough" in the interactions, which I can completely understand, being the one pulled around by everyone. This is a very, very good piece of work when you need to decorrelate the back…

Ah yes, the joy of maintaining open source software. I have seen many devs burn out over the requests made of them. I didn't know it was just one maintainer. That can both be a good thing for keeping the product focused, but it is also worrying, as that's a single point of failure. Anything could happen and then the whole project might fall into disrepair. That factor alone would make me weary of overly relying on Po…

I have some open source I maintain, fortunately, it stays very niche so I am not overwhelmed. But I know the pain.

What you are saying about forks is very true. Some very good ideas were started, then semi-abandonned on the way and they ended up with incompatible forks, and finally all of this collapsed.

I have no idea what the correct model could be.

Re: Pocketbase – open-source realtime back end in 1 file

#132

I see Pocketbase, I upvote. Using it in a few production apps and it's been a very solid experience. Some breaking changes from time to time, but generally very solid. Also has a lot of extensibility built in. Sometimes you might hit a scenario where it doesn't provide what you need, which is when things can get a bit hairy, but nothing a skilled dev can't work around.

> nothing a skilled dev can't work around.

Agreed. Loved this FAQ notice:

"If you don't have the time to at least skim through the documentation and you plan to solely rely on some AI tool, then please do NOT use PocketBase!"

Re: Pocketbase – open-source realtime back end in 1 file

#134

I can mirror everyone singing praise to pocketbase here. Once you grasp the concepts (which map pretty closely to SQL concepts, with rules for row-based security), it is by far the easiest way IMO to create a maintainable, robust backend with direct auth integrations and a pleasant interface. I have around 5 instances of pocketbase running on a 10 USD/month Hetzner server, serving thousands of users a day without bre…

What kind of app do you use it for?

Re: Pocketbase – open-source realtime back end in 1 file

#135
post #121

Earlier quoted context omitted.

While that may be true, it is worth seriously checking the docs and working out what requirements you have or might have. Pocketbase does an awesome job of providing extensibility, likely most of the stuff you want that’s not fully out of the box can be added in 20 lines of code or so.

So, that sits firmly where Django/Rails are at, except that you use a GUI rather than code to define the models? I suppose that lowers the bar ever so slightly, because any management rule or business logic is still deferred to a proper framework/programming language. Seems very niche and limiting, all things considered.

I wouldn't group it with Django. It's a very simple but also well-done CMS. It is not as capable as something like Wagtail, Payload, or Craft.

Re: Pocketbase – open-source realtime back end in 1 file

#136
I would like to try this. I have tried sqlite and duckdb, both got me started really quickly for an MVP, but then I quickly wished I had MVP’d with supabase because the step of backing up and productionizing was a lot of walking backwards. Maybe just me.

Re: Pocketbase – open-source realtime back end in 1 file

#137

I'm a huge fan of Pocketbase. Backing up the sqlite though had me more stressed than I'd prefer, and I wanted a plug-and-play way to sqlite3_rsync a backup while Pocketbase was running: so I've been working on this: https://sqlrsync.com . MVP works. Billing isn't being checked yet (be gentle but it's Cloudflare Durable Objects underneath so it should be local, fast, and resilient.) Would love feedback from anyone ope…

What are the differences between sqlrsync and litestream?

There’s a high level comparison here [1] but it doesn’t go into much detail about the architecture decisions. TLDR; litestream is continuous, sqlitersync is run as a command.

Re: Pocketbase – open-source realtime back end in 1 file

#138

I see Pocketbase, I upvote. Using it in a few production apps and it's been a very solid experience. Some breaking changes from time to time, but generally very solid. Also has a lot of extensibility built in. Sometimes you might hit a scenario where it doesn't provide what you need, which is when things can get a bit hairy, but nothing a skilled dev can't work around.

> nothing a skilled dev can't work around. Agreed. Loved this FAQ notice: "If you don't have the time to at least skim through the documentation and you plan to solely rely on some AI tool, then please do NOT use PocketBase!"

[flagged]

Re: Pocketbase – open-source realtime back end in 1 file

#139
post #95
post #84

Earlier quoted context omitted.

They said they hacked a Gemini server, Lagrange is a Geminispace browser. https://github.com/skyjake/lagrange

I also somehow thought a Google Gemini MCP server.

So did I. I know Gemini the protocol exists, but the reality is, in almost every context "Gemini" is so much, much more likely to refer to Google's LLM that I'm taken aback when it doesn't.

Re: Pocketbase – open-source realtime back end in 1 file

#140

I'm a huge fan of Pocketbase. Backing up the sqlite though had me more stressed than I'd prefer, and I wanted a plug-and-play way to sqlite3_rsync a backup while Pocketbase was running: so I've been working on this: https://sqlrsync.com . MVP works. Billing isn't being checked yet (be gentle but it's Cloudflare Durable Objects underneath so it should be local, fast, and resilient.) Would love feedback from anyone ope…

Sorry if my question is misguided: did you try SQLite3's native online backup API? I would not use raw file access knowing they have that.
Post reply on HN