Suggestion: Remove dependency of supabase

[Andersama]

I see that this hasn't really been actively developed in the last year or so, but my suggestion if any would be to try to get primo to be executable entirely locally.

This is a bit of a split to improve on the user experience for developers*, not necessarily companies, organizations or non-tech savy individuals who'd like to try this project out.

Note: you also need to update the website with the instruction to change the URL as the last step. I suspect that's actually what's causing me my current problem which is, I tried to get this running locally, and it seemingly mostly worked.

Now I don't know how tightly integrated primo is to supabase, or postgres, so this could likely be a huge undertaking, but I'd like to see a configuration option for using a database directly. Ideally the project as a whole should be launchable via npm run dev, straight from after having been cloned. This might be easier to do with a file-based database like sqlite.

The "best" experience would be to be able to configure supabase / postgres or another database AFTER the project's been launched, make that an optional part of the setup process, and then be able to copy all the work, data to the new database.

[acidlake]

maybe i can get it worked with pocketbase, that way can work without supabase

[nicosql]

maybe i can get it worked with pocketbase, that way can work without supabase

with 1.23 release of PB, this is now an even better idea than before - basically added avenues to use other data stores alongside sqlite. I use it with Turso, embedded our entire company site (also a svelte app) in the binary lol it's awesome.

[elemdos]

There's an existing discussion for this here: https://github.com/weave-cms/weavecms/discussions/295

It's been attempted in the past but never got very far. Tbh with version 3 out I'd rather focus on core functionality & stability instead of taking on something big like this, but anyone's free to fork & I'd be happy to offer guidance. I've made efforts to decouple the database/deployment target so it's partially there.