81–90 of 151 posts
Looks like a single executable, the admin interface and the database I can store on my laptop (and add it to my backup) is all I was looking for. Thank you for PocketBase and thank you for sharing it.
That's why I always come back to HN :-)
Earlier quoted context omitted.
I didn't say it's better. Why are people always misinterperting what they read (it's like you've never had text interpretation classes at school, or logic lessons to undestand how to infer implications from logical statements correctly)? Please read again: I said it's vastly simpler (which may not be better for you!) and lighter (just measure it). The comparison is apt for me because the description "open-source back…
Your initial comment presents Redbean as a comparable solution, which it's not; they serve very different use cases. Redbean requires you to write server code; Pocketbase does not. Redbean does not offer a realtime database, authentication, an admin dashboard, integrated file storage, or an inbuilt API. I like Redbean, but it's in a completely different "market sector". It's like comparing a kit car to a luxury car:…
> It's like comparing a kit car to a luxury car
If all I need is a bicycle, a kit car is already over the top but will do. A luxury car makes no sense. You're thinking like everyone has the same needs that you have or something.
Earlier quoted context omitted.
More than one server. Sqlite should be thread safe and simple services can scale to thousands of parallal users. If you are OK with some downtime every 6 months when server goes down it will scale well. Deploy/ rollback will be an effort.
Downside with separate SQLite databases will be when you want to have statistics over many users.
Where does it come from?
Why is it useful here?
What are the alternatives? Advantages/Drawbacks?
Is there an article somewhere, outside of the Pocketbase docs, presenting that pattern?
- https://github.com/pocketbase/pocketbase/blob/master/core/ap...
- https://github.com/pocketbase/pocketbase/tree/master/tools/h...
I am a bit confused, is it the backend's backend? E.g. something that is used by the HTTP server app, like a DBMS would be? Or is it actually the backend, e.g. the frontend (browser) talks to it directly?
You would use it instead of things like Supabase and Appwrite. It gives you a server, a db and easy authentication, authorization with real-time queries like firebase.
What are the pros/cons of this over firebase?
Cons: - you need to take care of all the hosting, backups, etc - cant scale to infinity like firebase (but on the other hand when you reach that scale youe firebase bill will be huge anyway)
Earlier quoted context omitted.
I feel like super easy to host needs to be re-emphasized. We're talking about dropping a single binary into your server and you're off to the races. If only more things were so simple.
Didnt docker make this easy for all projects?