91–100 of 113 posts
Good luck with the project! Seems like you’ve got some good interest :-)
PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…
I'm doing something along these lines in Go with Postgres, but I'm definitely not as productive as you.
What do you think about Echo? Was it your first choice as a web framework? How in your opinion is better than Gin for example?
Out of curiosity, how much time did you spend building the admin dashboard? Did you have previous experience with Svelte?
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…
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 for future release.
Earlier quoted context omitted.
Member of the Supabase team! Would love to hear your pain points with local development. Always looking for feedback so that we may improve your experience.
Well all the UI stuff. It is super easy to add a column and change something fast with the UI when doing rapid development. But that piece is missing when developing locally. I have gone on to create 2 projects (one called local and one prod) and manually applying the changes. Would be nice to apply changes from one project to another. PocketBase here for example provides the UI locally too. That is the real selling…
Suitable as the basis for a CMS ?
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 next version of my other open source project - Presentator).
Any client SDKs for Android, iOS, React, etc.
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.
Congrats and thanks for sharing.
And it would also give me more time to focus on business logic instead of Auth - i will definitely try this in the future.
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 web app hasn't been updated in years and overall your project looks much more polished than mine.
Good job! Bookmarking ;)