Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from Supabase

blog.val.town

Post reply on HN
Print view View original

21–30 of 136 posts

Re: Migrating from Supabase

#21

Post by motoxpro »

Great read. Similar to my experience with Hasura. Migrations we’re better there but the row level security was a nightmare. Went to just a custom node backend with prisma and it’s a dream. No more writing tons of json rules and multiple views just to not query the email field.

Seems like these types of services are good for basic large scale crud applications, probably why you have Hasura pivoting to enterprise.

The quote at the end of going back the future is exactly how I felt. Will never use a Hasura/Supabase/etc again. Just makes things more difficult.

Re: Migrating from Supabase

#22

Post by simonw »

The documentation section here applies to so many products I've battled in the past.

> The command supabase db remote commit is documented as "Commit Remote Changes As A New Migration". The command supabase functions new is documented as "Create A New Function Locally." The documentation page is beautiful, but the words in it just aren't finished.

Great documentation is such a force multiplier for a product. It's so worthwhile investing in this.

Don't make your most dedicated users (the ones who get as far as consulting your documentation) guess how to use your thing!

Re: Migrating from Supabase

#23

Post by crooked-v »

omeze wrote: post #3

The local development & database migration story is Supabase's biggest weakness. I hate having to do migrations live in prod. The admin dashboard is just so much better than any alternative Postgres tooling that it's been worth using despite that. Takes care of the stuff I'd normally be sweating over when writing migrations like nullable fields / FK constraints / JSON formatting for default fields. Would be great if…

If you use the CLI, `supabase start` spins up a Docker instance built from all your migration .sql files [1].

If anything, I think the admin dashboard encouraging directly doing operations on the database is the biggest weakness of Supabase. I would much prefer being able to lock it down to purely CI-driven migrations.

[1]: https://supabase.com/docs/guides/getting-started/local-devel...

Re: Migrating from Supabase

#24

Post by primitivesuave »

kiwicopple wrote: post #15

hey hn, supabase ceo here the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments 1. Modifying the database in pr…

Let me just say that (for me) Supabase is one of the most exciting startups of the past couple years and I'm sure these issues will get ironed out eventually. I believe in your overall mission and am inspired by how much progress you all have made in just three years.

Re: Migrating from Supabase

#26

Post by kiwicopple »

simonw wrote: post #22

The documentation section here applies to so many products I've battled in the past. > The command supabase db remote commit is documented as "Commit Remote Changes As A New Migration". The command supabase functions new is documented as "Create A New Function Locally." The documentation page is beautiful, but the words in it just aren't finished. Great documentation is such a force multiplier for a product. It's so…

this is very fair criticism. We hired a Head of Docs in March. I hope the improvements are evident since he joined, both in content and in usability.

We have a long way to go, but we're working on it.

Re: Migrating from Supabase

#27

Post by ahachete »

A mid way could be self-hosting Supabase, whether you use more or less Supabase features.

I know self-hosting might be challenging, specially getting a production-ready Postgres backend for it.

That's why at StackGres we have built a Runbook [1] and companion blog post [2] to help you run Supabase on Kubernetes. All required components are fully open source, so you are more than welcome to try it and give feedback if you are looking into this alternative.

[1]: https://stackgres.io/doc/latest/runbooks/supabase-stackgres/

[2]: https://stackgres.io/blog/running-supabase-on-top-of-stackgr...

update: edit

Post reply on HN