Live data from Hacker News

Show HN: PocketBase – Open Source realtime backend in one file

github.com

31–40 of 113 posts

Re: Show HN: PocketBase – Open Source realtime backend in one file

#32

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 confused about one detail: Does it render pages automatically based on Schema? I see your really simple example under examples, and its so minimal I want to think you just get all the tables and render views from that. Am I crazy? If so this is really neat. Did you ever consider using something like GORM? Because I could see this working with other databases and being extremely useful. I use Django to build reall…

"Collections" stores a single records table meta data (eg. name, fields, validators, etc.), so when you create a new collection a new related table will be created (see https://github.com/pocketbase/pocketbase/blob/3d07f0211dc747...).

The admin UI just shows the collections through the web api (https://pocketbase.io/docs/api-collections/).

I actually started with GORM, but its too complex and I ended up replacing it with a simpler query builder package (ozzo-dbx). While the query builder has abstraction for other databases, I'm not planning supporting them at the moment.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#33
post #30

I would love it. But: postgres, +backups, +replica managment. Basically a managed database for postgres in a container.

You may want to check Supabase or Nhost in that case.

PocketBase was specifically designed to be self-contained and running only on a single server.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#34

why is this written in Go , are there specific features that shine over Python3? I've been looking to learn Go, it seems lot of network intensive software use Go.

If a selling point is run from "one file", that's quite difficult to do in python. There are things like pyinstaller but you end up shipping the entire interpreter in the bundle.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#35

Wow, super impressed. I have always wanted to build something like this where everything is embedded in 1 single file and I knew Go could be a great way to do it but always wondered how to handle the database part. Along comes SQLlite. One feedback which will probably deviate from everything in 1 file concept but adding an option to upload files to an S3 URL will be awesome. Perhaps a pull request ? I am thinking of…

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?

Re: Show HN: PocketBase – Open Source realtime backend in one file

#36

Wow, super impressed. I have always wanted to build something like this where everything is embedded in 1 single file and I knew Go could be a great way to do it but always wondered how to handle the database part. Along comes SQLlite. One feedback which will probably deviate from everything in 1 file concept but adding an option to upload files to an S3 URL will be awesome. Perhaps a pull request ? I am thinking of…

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.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#37
this looks really great! i had recently been thinking “boy it’d be really great if there were a ‘supabase but sqlite’ available” and here you are! now i just need a clever project as an excuse to use this.

1 question: are the docs in a repo anywhere? i don’t see them in the main repo (i might just be missing them somehow) or anywhere in the org. if they are public somewhere would you be open to a docs polishing PR?

Re: Show HN: PocketBase – Open Source realtime backend in one file

#38

Wow, super impressed. I have always wanted to build something like this where everything is embedded in 1 single file and I knew Go could be a great way to do it but always wondered how to handle the database part. Along comes SQLlite. One feedback which will probably deviate from everything in 1 file concept but adding an option to upload files to an S3 URL will be awesome. Perhaps a pull request ? I am thinking of…

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?

Uploaded files and your database are stored outside of the binary.

Re: Show HN: PocketBase – Open Source realtime backend in one file

#39

Earlier quoted context omitted.

I'm confused about one detail: Does it render pages automatically based on Schema? I see your really simple example under examples, and its so minimal I want to think you just get all the tables and render views from that. Am I crazy? If so this is really neat. Did you ever consider using something like GORM? Because I could see this working with other databases and being extremely useful. I use Django to build reall…

"Collections" stores a single records table meta data (eg. name, fields, validators, etc.), so when you create a new collection a new related table will be created (see https://github.com/pocketbase/pocketbase/blob/3d07f0211dc747... ). The admin UI just shows the collections through the web api ( https://pocketbase.io/docs/api-collections/ ). I actually started with GORM, but its too complex and I ended up replacing…

No worries, I've seen another project called UAdmin that kind of reminds me of this, my problem with UAdmin was that there were bugs and I didn't quite get why it worked how it worked, but having used Django since I realized what I was missing out on.

Thank you for following up, I did see you had a package for extending the built-in Go package for SQL.

Post reply on HN