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?
It can be the backend itself if you just need auth (both authentication and authorization) and your SQL tables to be a REST API. This often suits frontend single page applications in JS/TS and Pocketbase also provides a JS SDK to ease this (with realtime updates). It's a similar model to Firebase but without the lock-in. However if you want to write more logic you can also import Pocketbase as a library and extend it…
Pocketbase: Open-source back end in one file
91–100 of 151 posts
Re: Pocketbase: Open-source back end in one file
#92Earlier quoted context omitted.
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.
Maybe it's not for me, I really don't know what that means. If it only describes itself as "a replacement for " I feel like I'm not the target at all.
Re: Pocketbase: Open-source back end in one file
#93Re: Pocketbase: Open-source back end in one file
#94Aren't there entire classes of problems that shouldn't exist for SQLite because it's intended to be an embedded database, as opposed to a client/server architecture like Postgres/Supabase?
And as such, I'm confused why this exists.
Re: Pocketbase: Open-source back end in one file
#95Been using Pocketbase for almost all of my projects lately. Its realtime database is especially nice to introduce multiplayer functionality with relative ease. It plus SvelteKit has been a dream to get up and running using the JS SDK.
I’m curious how you’re integrating it with Sveltekit? Are you using Sveltekit just as a static generator?
For CRUD apps, sveltekits progressive enhancement and form actions make it quick to to add simple function to the page. You can store the pocketbase instance, pb, in locals and reference it all over the application.
For more multiplayer things, sticking a client-side subscription to a collection allows updates of elements that can be worked with/added/moved around etc.
Re: Pocketbase: Open-source back end in one file
#96Earlier quoted context omitted.
It's like saying nginx is better than superbase/firebase. Apples to oranges. You could replicate PocketBase in Readbean, but you would have to implement from scratch: - resources with CRUD API and real time subscriptions - admin UI - authz & authn system
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…
I think you would have gotten a more positive reaction if you said something like "As an alternative take on the idea of an "open-source backend in one file, redbean is a much simpler, vastly lighter one-file web server + sqlite DB: https://redbean.dev/" to make redbean isn't necessarily intended to be the same type of "open-source backend in one file"
Anyway, redbean does look really neat even if it's not necessarily totally interchangeable with pocketbase
Re: Pocketbase: Open-source back end in one file
#97Re: Pocketbase: Open-source back end in one file
#98Re: Pocketbase: Open-source back end in one file
#99The simplicity is simply mind boggling!
Going to give it a try!
Re: Pocketbase: Open-source back end in one file
#100I'm not sure I understand what exactly is. I like the tips, but I don't understand: is it an app that I can run on my local machine?
More importantly, it provides a JSON API (and a client library) for interacting with those collections.