Support alternatives to Supabase

[carstenjaksch]

Appwrite, for example, could be easily self-hosted with Coolify – alongside an alternative to Vercel/Netlify.

This would be a game changer for European businesses that need to rely on European infrastructure to comply with several (privacy) policies.

Supabase, Vercel, etc. are all based in the US.

[denyeo]

+1. Would make it possible for many more people/companies to adopt if it could use Postgres, MariaDB/MySQL, etc.

[mateomorris]

Definitely! Supabase was recently decoupled out to enable this. I think with a guide we can more easily enable contributions for other backends like AppWrite or Pocketbase.

[LucasGabrielBravo]

I'd like to try using Pocketbase, but I'm not sure how to implement it.

Is there already a guide somewhere? If not, do you have any tips on how I could start this?

[mateomorris]

Definitely! You should be able to just fork it and change a couple files for consuming/updating the data. I'll write out some instructions in the next couple days.

[mateomorris]

Okay so it was more work than I thought because of the backend/authentication aspects but I go it mostly working. I just had to move everything to do all the data fetching from the frontend for now to simplify things. It's in this branch: https://github.com/primocms/primo/tree/backend-agnosticism so you can go ahead and pull that and then you'll find all the Pocketbase-specific stuff in src/lib/providers/pocketbase. You'll see the commented supabase code there to see how things are done with supabase so you can do the equivalent with pocketbase. You'll probably run into some stuff I didn't think about so feel free to post here or message me on Discord if when/if you run into any issues and we can work through them 👍

[LucasGabrielBravo]

Thank you very much!!! I'll start right now.

I played around with @primocms/builder a bit today. I added a "More blocks" tab that works basically the same as the "Primo blocks" tab, but I make a request to an api that returns the json with the blocks.

Now I'll try to do the same thing, only using pocketbase as the cousin's API and the block API at the same time.

As soon as I have satisfactory results I will post it here.

[mateomorris]

That's awesome! I've been wanting to add a "Personal Blocks" library that gets shared across sites for a while now, so I'm looking forward to seeing your implementation.

[SrGeneroso]

This is awesome, nothing wrong with supabase, but this is a good start to make everything more customizable.
I guess by now this is hardcoded but in the future this could be set as a package.

[rallisf1]

I strongly believe this is a waste of effort and time. Supabase can already be self-hosted and it is not that expensive to begin with (assuming you need a paid plan). Sure it would be a nice feature for Primo v3 but for now I think we should all focus on UX and bug fixes.

[ICTServ]

@LucasGabrielBravo, thank you for adding PocketBase provider. Could you please share the pocketBase schema for primo in your backend-pocketbase?

[malipetek]

Hi, I am trying to modify repo to use it with directus.
I do not agree with using other backends is a waste of time, self hosted supabase is very clunky with multiple containers for just using it for primoso.
Adding multiple providers to same repo might be increasing complexity yes, but we can always maintain a fork (I am considering it for directus one) if decoupling abstraction of backend module is maintained in the original repository.