Live data from Hacker News

Pocketbase: Open-source back end in one file

pocketbase.io

41–50 of 151 posts

Re: Pocketbase: Open-source back end in one file

#41
I've skimmed at the docs, and it's not clear to me how it would deal with:

* Something like row-level access control, so that people can only access the data in tables that belong to them (say clients can only view their own purchases, and also not modify them after they checked them out).

* Integration with the rest of the world, e.g. sending email, acting on triggers, etc.

* Something like CSV export/import.

* Internationalization.

Would that all be possible? Straightforward? Do those all require extending (with go or js)?

Looks like a nice tool.

Re: Pocketbase: Open-source back end in one file

#42

What minimal front-ends are there that one could combine with this minimal back-end to provide a minimal end-to-end?

Depends on what you consider minimal, but I enjoy working with PocketBase and VanJS[1]. However there is no component library built in (if this is what you were asking for).

[1]: https://vanjs.org/

Re: Pocketbase: Open-source back end in one file

#43

I've skimmed at the docs, and it's not clear to me how it would deal with: * Something like row-level access control, so that people can only access the data in tables that belong to them (say clients can only view their own purchases, and also not modify them after they checked them out). * Integration with the rest of the world, e.g. sending email, acting on triggers, etc. * Something like CSV export/import. * Inte…

Check out

API Rules https://pocketbase.io/docs/api-rules-and-filters/#api-rules

Hooks https://pocketbase.io/docs/js-overview/

Admin panel has backups for data, and import/export of collections schema

Re: Pocketbase: Open-source back end in one file

#44

I've skimmed at the docs, and it's not clear to me how it would deal with: * Something like row-level access control, so that people can only access the data in tables that belong to them (say clients can only view their own purchases, and also not modify them after they checked them out). * Integration with the rest of the world, e.g. sending email, acting on triggers, etc. * Something like CSV export/import. * Inte…

The first point (authn) is inherent to the unextended framework via filter rules.

Most of the remainder requires extension other than authz emails, but extension at its simplest just means adding a plain old JavaScript function to run on a record lifecycle event of some kind - typically [before/after] [insert/update/delete] of . Various GO APIs are exposed to the JavaScript runtime for doing filesystem, cryptography, http, email, etc work.

For i18n you have templates and a database.

Re: Pocketbase: Open-source back end in one file

#45
post #29
post #9

It seems to me that redbean is a much simpler, vastly lighter one-file web server + sqlite DB: https://redbean.dev/ As a bonus, the same file runs on basically any OS without any dependencies on the local system, not even libc.

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 backend in one file" matches both projects well and it's something I'm interested in, with readbean being far closer to my alley.

Re: Pocketbase: Open-source back end in one file

#49
post #10

I mostly know Python. Is there something similar in Python? Or the backend language is not relevant, because you mostly use this from JavaScript anyway?

I have been building a project https://github.com/claceio/clace which aims to make building hypermedia based web applications easier. Clace is implemented in go, it uses Starlark (python syntax subset) for application configuration. With Clace, the apps are implemented using Starlark and (go) html templates, HTMX is used for web interface, app developer does not need to write any JavaScript.

Re: Pocketbase: Open-source back end in one file

#50

It is great to see the number of good opensource projects in this area. Grist and NocoDB deserve mentions, although more targeted towards database management. It is also amazing that they provide so simple ways to get started (single file/electron) - https://github.com/gristlabs - https://nocodb.com/

Did not know about either of those, thanks. I've been using Baserow for small projects that I believe Pocketbase is a way better fit.
Post reply on HN