Running without PocketBase?

[dan-pagan]

How much work would it be to use spatz-2 without the user management features provided by PocketBase. I am looking for a boilerplate that uses shadcn-svelte, superforms, etc. but don't need user management. I realise that Pocketbase is lightweight, but I'd rather not add unused dependencies if possible. ty.

[engageintellect]

You could spin up it up and get rid of the pocketbase hooks, and the routes that use it. Not a huge amount of work. But it would probably be easier to just spin up a blank sveltekit project and add shadcn-svelte, superforms and whatever else you want.

I'm lazy though. So when I have a use case that doesn't require user management, I just bypass the login/registration screens. There is an "if" statement in /src/routes/+page.svelte that checks to see if the user is logged in, in order to decide what UI to render... I just get rid of the part.

It's easier for me to leave all the the pocketbase plumbing in and not need it, than to need it and not have it. And if I need to track users in the future - it makes it easy to "turn on".

Hope this helps. Happy to answer any questions I can.

[dan-pagan]

Thanks for the reply. I like the structure and agree with you that it's probably easier to leave it in, I was just asking in case it was something you had done or considered. I prefer to take the easier route also, which is why I am looking at your boilerplate project rather than rolling my own.

In the future, maybe a basic setup script to allow users to select some of the non core features would be useful. So if you are just making a simple 'flyer' site for example you could turn of things like user auth. Just an idea.

I've been away from the Svelte ecosystem for a year so I need to get back up to speed with Svelte5 and other changes. Thanks for sharing your boilerplate project. This looks like a good place to get (re)started.

[keesfluitman]

Just wanted to give you a thanks. Learned a lot from your Project. Im just a hobbyist, but currently trying to convert it to a partly SPA. Since that is what the pocketbase creator also recommends. Im adding subscribing to changes in pocketbase directly and it seems a bit more logical to do most pocketbase interactions directly with pocketbase anyway. Sveltekit is just a proxy anyway for all PB requests and responses right now.

I must say. It was a bit confusing that you say this project is Svelte5 now. Since a lot still uses legacy code and stores. Maybe you could add that to the readme. Otherwise great work! And thanks for sharing.