If anyone is interested in extending I have done some work on it and can confirm it is quite easy. I extended it to be able to use stripe check it out below:
Pocketbase: Open-source back end in one file
131–140 of 151 posts
Re: Pocketbase: Open-source back end in one file
#132[flagged]
Re: Pocketbase: Open-source back end in one file
#133Pocketbase is amazing, I had made a small starter with nuxt 3.
https://github.com/fayazara/pocketbase-nuxt
Example has 1. Auth 2. Route rules 3. CRUD actions 4. Realtime events 5. Storage
Needs refactoring but I really enjoyed working with it, I want to add stripe subscriptions to this taking routes rules to it's limits, not sure how yet, will figure it out.
Re: Pocketbase: Open-source back end in one file
#134this is great. What would be the frontend equivalent? A simple, no bells and whistles frontend to throw something together quickly?
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?
Re: Pocketbase: Open-source back end in one file
#135Earlier quoted context omitted.
PocketBase is trying to be a simple webserver, code-running backend, and database. I believe the author chose SQLite because it is simple. PocketBase isn't trying to have every feature nor be high performance.
Like Althttpd? That’s the web server created by the SQLite team and also serves sqlite.org https://sqlite.org/althttpd/doc/trunk/althttpd.md
Thanks for bringing it to my attention, never heard of it before. Have you used it?
Re: Pocketbase: Open-source back end in one file
#136How are database migrations handled in this? Ive never understood how BaaSes are to be used when I need to add a new column to my table and do some inserts into it in the same migration
PocketBase has a pb_migrations/ directory. If you throw a file of a certain format, PocketBase will automatically loaded it and update the DB.
Oh neat, that would absolutely do the job. Just git push and let the gitops do the rest!
Re: Pocketbase: Open-source back end in one file
#137Can this thing be used for a forum type site + a minimal game feature with around 5k daily users? How could you scale this with a single common database?
Re: Pocketbase: Open-source back end in one file
#138I've been developing on PocketBase for 2 months. The system goes into production in 1 to 2 months. I'm exceptionally happy with it. I'm developing an webapp for a friend's company and wanted a very simple system to hand-off. The whole thing is running with one binary: Pocketbase. It runs a webserver, server-side Javascript (compiled TypeScript) code, and SQLite database. The single process is hosted on Vultr for $12…
> And, as part of my contract, my friend's company will donate to Pocketbase. :)
What a positive way to give back! Kudos!
Re: Pocketbase: Open-source back end in one file
#139Can this thing be used for a forum type site + a minimal game feature with around 5k daily users? How could you scale this with a single common database?
5k daily users is basically nothing. Pocketbase would probably work well for you.
Re: Pocketbase: Open-source back end in one file
#140I'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…
I've been developing for PocketBase for 2 months. As someone else mentioned, API rules can control access to rows. It can send emails. Set timers. And send its own requests to other webservers. (I haven't used any of these features.) https://pocketbase.io/docs/js-sending-emails/ I had to write my own CSV importer. (I'm hoping to open-source it.) As for internationalization, what specific features did you want? That s…
Re internationalization, I think you're right. I don't have experience building app/websites, a fortiori with internationalization, so I threw this question in with the lot!