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

Supabase Local Dev: migrations, branching, and observability

supabase.com

Post reply on HN
Print view View original

21–30 of 57 posts

Re: Supabase Local Dev: migrations, branching, and observability

#21

Post by thewataccount »

kiwicopple wrote: post #2

hey hn, supabase ceo here a few months ago one of customers migrated away from supabase and they wrote a blog post about it. That blog post appeared here[0] on hacker news. many of the issues they encountered were related to local development. we made several promises to improve based on that feedback and the various comments in the HN thread today’s launch delivers on many of those promises. We’ve added better suppo…

I checked a little bit ago but I might have missed it so please correct me.

Are there plans to expand self-hosting support? The migrations are a big step forward.

Are you intending to fill the roll of being a framework akin to a "super django" type of deal? Again the migrations help a ton, but I've been hesitant to use Supabase for random projects because I don't want to rely on the platform, and I don't want random people on github who want to try or contribute to require a supabase account.

I'd love to use it more as a modular ORM for miscellaneous projects instead of the current "hosted platform", currently none of the tutorials (or github projects) seem to explain this route at all.

I think you actually do work for this purpose, and I think the docs mostly cover the bare minimum for self hosting, and I understand your business kinda relies on the hosted platform, but I'd love to see further tutorials and thorough explinations of all the features - currently some like the AI features aren't really explained if they work in the self-hosted or not, or if you have to do anything special for that.

EDIT: Also I do appreciate your business being opensource, and contributing to postgres so much! Sorry for the rambling, and I apologize if I'm blind and missed some obvious docs.

Re: Supabase Local Dev: migrations, branching, and observability

#22

Post by kiwicopple »

rrgok wrote: post #14

I hate to be this guy, really. I would like to adopt Supabase in my company, but I cannot yet. I commented on a HN post almost a year ago about how hard is to do custom Auth with Supabase. I still haven't find a good solution about it. For example, LDAP Auth is quite crucial in most enterprise settings, yet I have no idea how to do it with Supabase. I can find a workaround for PostgREST by putting a secondary API wri…

> Even if it is not specifically for LDAP, make some API available to do so, please.

Based on the issue (title and comment), it seems that you have asked specifically for LDAP support rather than a generic API.

Feel free to share some more details in the github issue, so the Auth team can figure out how best to support you. It looks like they have followed up asking for the use-case and they are just waiting for some clarifying details.

Re: Supabase Local Dev: migrations, branching, and observability

#23

Post by ilrwbwrkhv »

kiwicopple wrote: post #22
rrgok wrote: post #14

I hate to be this guy, really. I would like to adopt Supabase in my company, but I cannot yet. I commented on a HN post almost a year ago about how hard is to do custom Auth with Supabase. I still haven't find a good solution about it. For example, LDAP Auth is quite crucial in most enterprise settings, yet I have no idea how to do it with Supabase. I can find a workaround for PostgREST by putting a secondary API wri…

> Even if it is not specifically for LDAP, make some API available to do so, please. Based on the issue (title and comment), it seems that you have asked specifically for LDAP support rather than a generic API. Feel free to share some more details in the github issue, so the Auth team can figure out how best to support you. It looks like they have followed up asking for the use-case and they are just waiting for some…

One killer feature from Firebase is anonymous authentication https://firebase.google.com/docs/auth/web/anonymous-auth

This allows for a frictionless onboarding process for startups.

Are there plans for Supabase to support that?

Re: Supabase Local Dev: migrations, branching, and observability

#24

Post by kiwicopple »

thewataccount wrote: post #21
kiwicopple wrote: post #2

hey hn, supabase ceo here a few months ago one of customers migrated away from supabase and they wrote a blog post about it. That blog post appeared here[0] on hacker news. many of the issues they encountered were related to local development. we made several promises to improve based on that feedback and the various comments in the HN thread today’s launch delivers on many of those promises. We’ve added better suppo…

I checked a little bit ago but I might have missed it so please correct me. Are there plans to expand self-hosting support? The migrations are a big step forward. Are you intending to fill the roll of being a framework akin to a "super django" type of deal? Again the migrations help a ton, but I've been hesitant to use Supabase for random projects because I don't want to rely on the platform, and I don't want random…

> Are you intending to fill the roll of being a framework akin to a "super django" type of deal?

We don't plan to replace any specific framework. We simply want to make Postgres easier to use. You can use Django (or any other framework) and Supabase together. We provide some additional tooling on top, but we aim to make this tooling 100% compatible with other tools. As an example, here[1] is a change we made recently so that our Storage service works better with Clerk (a popular Auth service, which is a good alternative to our own Auth service). We plan to document this better - it was one of the promises I made in the OP.

> Are there plans to expand self-hosting support?

we made a few updates[0] this week to improve self-hosting based on the common feedback. if there is anything missing just let me know and i will do another round of improvements.

> currently some like the AI features aren't really explained if they work in the self-hosted or not, or if you have to do anything special for that.

nothing is feature-gated so everything works on self-hosted. That said, I agree that we can be better at explaining the self-hosting. We are putting a lot more effort into improving our docs in general. For self-hosting we can certainly be clearer about the boundaries where you are responsible (eg, you need to take care of your own backups, the AI features will require external acconts). we're working on this, but feel free to open issues where it's unclear we can address anything specific

[0] https://github.com/supabase/supabase/pull/16097

[1] https://github.com/supabase/storage-api/pull/340

Re: Supabase Local Dev: migrations, branching, and observability

#25

Post by kiwicopple »

ilrwbwrkhv wrote: post #23
kiwicopple wrote: post #22

Earlier quoted context omitted.

> Even if it is not specifically for LDAP, make some API available to do so, please. Based on the issue (title and comment), it seems that you have asked specifically for LDAP support rather than a generic API. Feel free to share some more details in the github issue, so the Auth team can figure out how best to support you. It looks like they have followed up asking for the use-case and they are just waiting for some…

One killer feature from Firebase is anonymous authentication https://firebase.google.com/docs/auth/web/anonymous-auth This allows for a frictionless onboarding process for startups. Are there plans for Supabase to support that?

that's on the roadmap - definitely one of our most requested Auth features. I don't have a timeline yet, but I know it's somewhere at the top of the (kanban) list for the Auth team

Re: Supabase Local Dev: migrations, branching, and observability

#27

Post by kiwicopple »

random_kris wrote: post #26

I cannot decide what to do on my project. Use drizzle as orm and supabase just as a nice wrapper around my PG db. Or go fully into supabase ecosystems and also use their types and their built in migrations and types

they should be compatible, so I don't think you need to see it as an either/or. If you choose to use both however, then you should use drizzle to scaffold your database.

Our clients will work with the drizzle-generated tables (since they use PostgREST).

Re: Supabase Local Dev: migrations, branching, and observability

#28

Post by kiwicopple »

nathancahill wrote: post #17
kiwicopple wrote: post #2

hey hn, supabase ceo here a few months ago one of customers migrated away from supabase and they wrote a blog post about it. That blog post appeared here[0] on hacker news. many of the issues they encountered were related to local development. we made several promises to improve based on that feedback and the various comments in the HN thread today’s launch delivers on many of those promises. We’ve added better suppo…

Massive congrats on shipping this. Will really improve the DevEx. Are you hiring?

I don't think we have any positions open currently unfortunately, although we're always looking for talented SREs & support to keep up with the platform growth. feel free to reach out (my details are in my profile)

Re: Supabase Local Dev: migrations, branching, and observability

#29

Post by kiwicopple »

jadbox wrote: post #6
kiwicopple wrote: post #2

hey hn, supabase ceo here a few months ago one of customers migrated away from supabase and they wrote a blog post about it. That blog post appeared here[0] on hacker news. many of the issues they encountered were related to local development. we made several promises to improve based on that feedback and the various comments in the HN thread today’s launch delivers on many of those promises. We’ve added better suppo…

After being burned by other DaaS providers (looking at you AWS Amplify/Cognito), I've been skeptical to use anything other than rolling my own solutions. Supabase updates does continue to impress, and I do really appreciate these improvements to local development.

> rolling my own solutions

I would love to hear what solutions you're choosing.

one of our goals is to provide only the tools/tech/features that you'd choose yourself or need to build to get started. If you're skeptical based on our technology choices then it's useful to receive that feedback

Re: Supabase Local Dev: migrations, branching, and observability

#30

Post by soultrees »

kiwicopple wrote: post #2

hey hn, supabase ceo here a few months ago one of customers migrated away from supabase and they wrote a blog post about it. That blog post appeared here[0] on hacker news. many of the issues they encountered were related to local development. we made several promises to improve based on that feedback and the various comments in the HN thread today’s launch delivers on many of those promises. We’ve added better suppo…

Respect. This is how you build a winning product and make your users feel heard. Take note upcoming class.
Post reply on HN