> There are so many projects I could use pocketbase for, if only it supported Postgres.
replySo... you want Supabase? which is what Pocketbase is inspired by.
It's not single binary, you need to spin up a dozen or so containers and have a full DevOps team on standby if self hosting.
replyYes, OP wants to hand the database to their team.
replyNo. OP said they want to handle the database to their team. They didn't say anything about the auth, analytics, admin dashboards, real time change data management proxies, connection poolers to their team. Your modern backend as a service that's not pocketbase usually has a dozen moving parts.
replyMost enterprise teams have plug and play SQL databases ready to go, anything else would require more work with DevOps.
Well yeah, that's the nature of using something like Supabase it is designed to scale and be flexible to develop on top of.
replyI am also building similar product but with different approach
And just using SQLite for now but plan on adding Postgres support ( orm I am using supports it ) … but nowhere near production ready. Due to buzz around products like litestream I feel like just SQLite is also viable nowadays. I also have own cdc based replication thing wip but yeah just having fun stage
replylike others have said, try sup abase
replyhttps://supabase.com/docs/guides/self-hosting/docker
i havent tried self hosting but it doesn't look too tricky
setup is easy but you're stuck with one instance. they stripped all multi-tenant features and even the selfhosted version is missing essential features, scaling is off the table though.
replySupabase? https://supabase.com/
reply