mateomorris
commented
10 months ago Glad you're liking it! To address your points individually:
- Supabase is still easier than Pocketbase because Pocketbase doesn't offer a free cloud service. But there's an active effort to add decouple Supabase and enable Pocketbase. I'd recommend adding your points to the existing discussion.
- Check out the existing discussion about Tailwind - it's got instructions on how to enable Tailwind in Primo. The tldr for not embedding support is that it's a lot of work, but maybe it'll be possible in the future with plugins.
- By the primo API - I'm guessing you mean the 'Primo Blocks'? Could you open a discussion for that? I think we're going to have a 'Community Blocks' and/or 'Personal Blocks'
- Not sure what you mean by "there is start script for production that uses built static files after using vite build" - could you open a separate issue for that?
There's a lot of topics here so I'll let you add to the existing discussions / create new discussions/issues for each & close this. See you there :)
I tried to use primo and really it's very handy tool. But I didn't like that it's dependent on Supabase and cloud host like vercel. Primo uses small database and storage. PocketBase is a single binary BaaS that has all features you are using on Supabase. It's a simple BaaS alternative to Supabase. PocketBase doen't have any process to install, download single binary and run ./pocketbase serve that's it! Also Tailwind CSS has a huge ecosystem. For example, I'm using shuffle.dev template builder and I'm thinking to contribute to this primo templates those templates I built using shuffle.dev. Also it would be better if you make the primo API repo available to contributors, so developers like me can add template and link to the API. And make build process easy for local. At the moment there is start script for production that uses built static files after using vite build.
PocketBase: https://pocketbase.io/ Tailwind CSS templates: https://shuffle.dev/new?editor=tailwind