Live data from Hacker News

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

github.com

41–50 of 113 posts

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

#41

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…

feedback: re the site:

i have no idea what you mean by a "backend". If it's got a "admin dashboard" it's got a UI which means it's got a front-end which means it's not a backend. I'm assuming "go backend" isn't specific to go but just indicating that it's written in go.

it's got a example code block but doesn't explain the point of it. Why would an existing framework with a UI and everything need me to write a `main` method? Why doesn't it have one already? If it doesn't have one why doesn't it. If it does have one why am i not using it? My thinking here is that there are many existing patterns for registering plugins / extended functionality that don't require altering the main method of the thing you're hooking into. Why aren't you using that? Is this maybe intended to be like... a starter template for a Sinatra like thing with a pre-defined set of functionalty? Kind-of like how Django sets up model administration UIs for you?

re your summary here and the site:

i have no idea what "backed-in files" means and I've been doing web-dev for decades.

"convenient Admin dashboard UI" ... to admin / do what?

"simple REST-ish API" a) why "ish" and not actually REST b) ... that let's me do what?

--- in summary.... this looks useful but i don't get what you're actually offering or what it's intended usage scenario is. This is compounded by the fact that you're using a very atypical definition of one word "backend" and a very uncommon term "backed-in files"

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

#42

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?

The documentation is not auto generated and is part of the static landing site (built with SvelteKit).

I didn't bother open source it because it is kinda messy and a little complicated to be edited by users not familiar with the codebase, but I'll try to find some time in the future and may publish it.

In the meantime, if you find typos or think that some of the wording could be improved, feel free to open an issue or discussion in the main repo and I'll fix them.

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

#44

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…

feedback: the "in one file" marketing confused me for a bit until i realized you meant "as a single binary". i would say that instead.

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

#45

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…

feedback: re the site: i have no idea what you mean by a "backend". If it's got a "admin dashboard" it's got a UI which means it's got a front-end which means it's not a backend. I'm assuming "go backend" isn't specific to go but just indicating that it's written in go. it's got a example code block but doesn't explain the point of it. Why would an existing framework with a UI and everything need me to write a `main`…

It's a lightweight replacement for Firebase. I That's why it is described as a backend, because it's primary feature is to act as a data store. If don't understand what a project does, and you're unfamiliar with the comparisons given (Firebase, Supabase), the right thing to do would bw to look up the comparisons.

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

#46

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…

feedback: re the site: i have no idea what you mean by a "backend". If it's got a "admin dashboard" it's got a UI which means it's got a front-end which means it's not a backend. I'm assuming "go backend" isn't specific to go but just indicating that it's written in go. it's got a example code block but doesn't explain the point of it. Why would an existing framework with a UI and everything need me to write a `main`…

You haven’t tried really hard:

> PocketBase could be used as a standalone app or as a Go framework/toolkit that enables you to build your own custom app specific business logic and still have a single portable executable at the end.

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

#47

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…

> backed-in files and users management

Did you intend to say baked-in? Like it's built-in? If so, I feel it's better to just use "built-in" because it's more familiar. The same typo's in the site too and confused me a bit.

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

#49
post #46

Earlier quoted context omitted.

feedback: re the site: i have no idea what you mean by a "backend". If it's got a "admin dashboard" it's got a UI which means it's got a front-end which means it's not a backend. I'm assuming "go backend" isn't specific to go but just indicating that it's written in go. it's got a example code block but doesn't explain the point of it. Why would an existing framework with a UI and everything need me to write a `main`…

You haven’t tried really hard: > PocketBase could be used as a standalone app or as a Go framework/toolkit that enables you to build your own custom app specific business logic and still have a single portable executable at the end.

if it's used a standalone app then what functionality is it providing beyond "user admin". Like, what problem does it solve in that use case?

> a Go framework/toolkit that enables you to build your own custom app specific business logic

that definition applies to literally every framework and toolkit. It tells me nothing.

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

#50
post #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.

The pex tool lets you build single file python executables which are well suited for server deployments.
Post reply on HN