Nice project! It looks pretty similar to my own LiteStore: https://h3rald.com/litestore/ The feature set is pretty similar, but I focused mainly on the free form/nosql-ish aspect of it, and although I added support for server-side JavaScript middleware I didn't include authentication OOTB (although it could be implemented or you can integrate with an OAuth2 system - it can validate JWT tokens). And yes, LiteStore's w…
I notice that it has full text search support, too, which pocketbase doesn't seem to.
Potentially silly question (I'll go out on a limb anyway). I would like to create a multi-platform app for non-technical users where their data is transparently self-contained/self-hosted. So, they open a single binary and it presents them with a UI, and the data created from within the app would be stored in their local PocketBase database. However, I wouldn't want the user to have to start a server directly (they w…
There is already a JavaScript SDK ( https://github.com/pocketbase/js-sdk ) that works both in the browser and node. Dart SDK (targeting mainly Flutter) is also on the way. Unfortunately I'm not very uptodate with Android (Kotlin) or iOS (Swift) development and therefore community contributions are more than welcomed.
This looks really great. Have you thought about adding Operational Transform or CRDT primitives to your offering? Realtime subscriptions are nice - but they're even better with realtime collaboration. Because you're using SQLite directly, it's easy(er) for you to build in efficient CRDT mutations to your database rows because SQLite's BLOB column supports incremental IO: https://www.sqlite.org/c3ref/blob_open.html Th…
Currently any additional data transformation is left to the developers to extend via event hooks or custom client side handling. I've worked with CRDT in the past (yjs), but it may not be very useful in PocketBase considering that the application was designed to run on a single server and db writes are practically queued (you can have only one sqlite writer at a time). I'll investigate it further and may consider it…
I think if you integrate Yjs or a OT library first-party, you'll have a really exceptional framework - open source firebase alternative top-to-bottom, ready for "local-first" collaborate own-your-own-data apps. Sounds like my dream stack for small-scale projects or friend/family apps.
The existing admin interface could be used as a very rudimentary content management, but it was really intended for quick internal data explorations and edits. Additionally, currently there are no roles for admins so permission controls within the admin area are not possible. You could always implement your own custom CMS SPA frontend that interacts with the PocketBase API (that is how I'm planning to use it with the…
Maybe I open an issue for discussion. Mainly I wonder about making architectures mesh.
Uploaded files must deviate from „everything in one file“ regardless of using S3, right? How (and why) would you store user uploads within the binary?
yea it was a silly question. It does allow S3 anyway so we are good.
My intent was not to point out a „silly question“. I was legitimately interested if there is a reasoning and what a use case for that would be.
Thank you for responding nicely!
Looks very interesting! looks like document database, but how i can create indexes?
Currently you cannot create indexes through the admin UI, but it's in my todo. As an alternative, you can always create indexes through DB migrations or add the index directly via the `sqlite3` cli.
thanks for reply!
is it schema free? or i need to define scheme via migrations?
Currently you cannot create indexes through the admin UI, but it's in my todo. As an alternative, you can always create indexes through DB migrations or add the index directly via the `sqlite3` cli.
thanks for reply! is it schema free? or i need to define scheme via migrations?
Its not schema free (although you can create a json field and put whatever you want in it).