So it's just auth + files on top of a db, essentially providing auth'd CRUD with extras? So you write the business logic in the frontend?
Pocketbase: Open-source back end in one file
141–150 of 151 posts
Re: Pocketbase: Open-source back end in one file
#142I feel like this will be super interesting when pairing with static site generator such as eleventy. Using static site generator is sometimes difficult because of lacking a web backend and ghost is too heavy for me.
Could you explain a bit more this setup? I have been looking for a way to have a tool to fill pages for a static site generator that's local and then just git push in a simplified way. The idea is to create a website for my mother, without having to deal with hosting at all (static github pages). Does this combination work that way?
Yes.
Some static site generators have good support for generating pages from a dynamic source, say API, database or anything you can access using programming language.
See eleventy, for instance, has the “Javascript data files” [1], it run some JS code to generate a list of posts, here we can fetch from pocketbase, then, we can generate pages dynamically [2].
Pocketbase in this case just act as a lightweight CMS.
Is this what you’re talking about?
Re: Pocketbase: Open-source back end in one file
#143Earlier quoted context omitted.
Could you explain a bit more this setup? I have been looking for a way to have a tool to fill pages for a static site generator that's local and then just git push in a simplified way. The idea is to create a website for my mother, without having to deal with hosting at all (static github pages). Does this combination work that way?
No. PocketBase runs on a server. It needs a host. It is simple, so its single program is (1) a webserver, (2) runs server-side code, and (3) hosts a DB. I'm running a $12-per-month server on Vultr and its only service is PocketBase. You don't need to host the webpages on PocketBase. If you wanted all your webpages to be on Github Pages, you could do that.
You won’t need to really run server all the time, you can run locally and use it as a lightweight CMS, and run only when you need to edit and generating anything. You can choose to only upload the generated HTML files to GitHub.
See my explanation on my reply to the original post.
Re: Pocketbase: Open-source back end in one file
#144Earlier quoted context omitted.
Interesting! I haven't made anything serious yet with the PocketBase (mostly due to lack of time & not anything to do with PB). I'm curious to know what kind of projects did you build using PB and how was your development experience?
One of my production projects with around 20,000 customers and 400k arr runs on Pocketbase with zero issues. I cannot recommend it enough.
Is vertical scaling enough/do you have any concerns for the future?
Re: Pocketbase: Open-source back end in one file
#145I mostly know Python. Is there something similar in Python? Or the backend language is not relevant, because you mostly use this from JavaScript anyway?
Re: Pocketbase: Open-source back end in one file
#146Earlier quoted context omitted.
One of my production projects with around 20,000 customers and 400k arr runs on Pocketbase with zero issues. I cannot recommend it enough.
Is vertical scaling enough/do you have any concerns for the future?
Vertical scaling will be enough till I sell that business.
Re: Pocketbase: Open-source back end in one file
#147Earlier quoted context omitted.
Could you explain a bit more this setup? I have been looking for a way to have a tool to fill pages for a static site generator that's local and then just git push in a simplified way. The idea is to create a website for my mother, without having to deal with hosting at all (static github pages). Does this combination work that way?
Yes. Some static site generators have good support for generating pages from a dynamic source, say API, database or anything you can access using programming language. See eleventy, for instance, has the “Javascript data files” [1], it run some JS code to generate a list of posts, here we can fetch from pocketbase, then, we can generate pages dynamically [2]. Pocketbase in this case just act as a lightweight CMS. Is…
Yes that is exactly what I was looking for. Amazing! Thank you
Re: Pocketbase: Open-source back end in one file
#148It 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.
I love redbean, just holding out for ARM support.
It's here! Download the nightly build, which is a fat binary for x86+arm:
wget https://cosmo.zip/pub/cosmos/bin/redbean
chmod +x redbean
./redbean
Re: Pocketbase: Open-source back end in one file
#149Earlier quoted context omitted.
I was happy with Svelte. But it only does single-page apps. But it's simple and the tutorial is delightful. When I moved to multiple pages, I had to use SvelteKit, which is complicated and not well documented.
When was the last time you used SvelteKit?
Today.
Re: Pocketbase: Open-source back end in one file
#150Earlier quoted context omitted.
I love redbean, just holding out for ARM support.
It's here! Download the nightly build, which is a fat binary for x86+arm: wget https://cosmo.zip/pub/cosmos/bin/redbean chmod +x redbean ./redbean Enjoy! I'll get a release out on redbean.dev soon.
Best late X-Mas present ever. :) Thank you.