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

We are moving to General Availability

supabase.com

Post reply on HN
Print view View original

71–80 of 106 posts

Re: We are moving to General Availability

#71

Post by jddj »

waldrews wrote: post #65
kiwicopple wrote: post #57

Earlier quoted context omitted.

let me have another run at it: > If you use Postgres you're "locked" into Postgres: a technology with a laundry list of providers. Supabase is just a Postgres platform, and you can use it like that so that you can migrate away to any one of those laundry list. We _also_ provide some tools which are nicely integrated but importantly: they are optional > doesn't Supabase rely on spinning up additional services to leave…

Sorry, confused by the wording: what does 'spinning up' mean here?

Configure and begin running

Re: We are moving to General Availability

#72

Post by TOMDM »

davetron5000 wrote: post #70

I built a toy app using this, with a front-end only app and postgrest + RBS. The app was seriously two forms behind a login. It was a huge pain. RBS is "insecure by default" meaning if you don't set it up right, all users can access all data. And, because it's SQL, it's really easy to write a valid and successful configuration that doesn't work. You have to test it. And for views, you have to do some real heroics to…

A few things, RLS is secure by default, it's postgrest that's insecure by default.

RLS disables all operations on a table once enabled and is only operable once there's a passing policy unless you can bypass RLS.

When it comes to access control, you should probably always have tests for anything halfway important.

Views are a bit of a footgun when it comes to RLS, they bypass it by default. But getting them to play nice is as simple as defining "security invoker" in their definition; not what I'd call heroics.

Re: We are moving to General Availability

#73

Post by wirelesspotat »

k_vi wrote: post #55
jmeyer2k wrote: post #22

Congrats on the launch! Here's our experience with Supabase at https://automark.io (Next.js + Supabase). - First of all, Supabase let us launch fast which was amazing. Super powerful Postgres features without the pain of self-hosting (or so we thought). - We started out using their hosted product for both our DB, storage, auth, and functions. - Functions have a critical bug that prevent us from using in development s…

Tried Supabase but currently only use their Auth. The server to database latency was very high(few hundred ms) whereas Planetscale DB in the same region gives sub 10ms. Still great option for most projects that can do with these issues.

How far was the server from the Supabase instance?

I have a toy project with a server on Fly.io and the DB on Supabase within the same city

When sending API requests to the server, my end user latency was around 25ms-100ms (depending on the endpoint and how many DB calls it was doing)

Now with Supabase on Fly, that API latency is down to 17ms-70ms. But Supabase on Fly is still in alpha so it's not relevant for production yet

Re: We are moving to General Availability

#74

Post by TOMDM »

kiwicopple wrote: post #43
colordrops wrote: post #24

Earlier quoted context omitted.

> Supabase is one of the most portable platforms out there Not in my experience. The documentation and infra is just not there to make it easy to use an external postgres db.

we know of many, many companies using Supabase self-hosted or with an external database. if you have any problems, feel free to reach out to me directly. We want this to be simple (and you can see that there are non-supabase commentors in this thread who are self-hosting, so it's not just lip service)

I self host a couple supabase instances.

That said it feels like every other week there's an update that breaks the self hosted compose, looking through the GitHub issue tracker shows a few issues where the suggestion is "oh yeah the latest X image doesn't work, regress the version to get it running"

I really like supabase, but stability on the self hosted images is my biggest gripe with it currently.

Re: We are moving to General Availability

#76

Post by Jabbles »

kiwicopple wrote: post #2

hey hn, supabase ceo here we just announced GA, after ~4 years of beta. for those who don't know: supabase is a postgres hosting company. we also host other open source "backend" tools that make it easy to get started with postgres (tools like PostgREST for auto-generate APIs [0]) we owe a lot to the HN community. you launched us 4 years ago [1], when we were just a few developers. since then HN has been a staple in…

Why do you not use capital letters in the typical way?

Re: We are moving to General Availability

#77

Post by Takennickname »

Jabbles wrote: post #76
kiwicopple wrote: post #2

hey hn, supabase ceo here we just announced GA, after ~4 years of beta. for those who don't know: supabase is a postgres hosting company. we also host other open source "backend" tools that make it easy to get started with postgres (tools like PostgREST for auto-generate APIs [0]) we owe a lot to the HN community. you launched us 4 years ago [1], when we were just a few developers. since then HN has been a staple in…

Why do you not use capital letters in the typical way?

It is a little bit painful to read. Capital letters exist for a reason (to make reading easier)

Re: We are moving to General Availability

#78

Post by vbezhenar »

I'm not supabase client, so I guess my wishes do not matter much, but I'm self-hosting it and the experience was not pleasant. They just gave me some huge docker-compose with barely any documentation about it and that's about it. My approach to self-hosting software is carefully learn about every service I'm going to run, disabling everything not needed for my use-case. That was not possible with supabase without significant time investments.

So my wish would be for supabase to provide some kind of minimal bare-bones configuration and careful documentation for their monstrous docker-compose configuration with explanations why all parameters were set to non-default values. I don't think that I need all those services if I don't use any of them except database and sometimes admin UI.

Also I think that I even had to edit some configs for api keys or something like that. It should not be like that, everything should be passed down via envs.

Right now I've set up supabase for our developers but asked them to migrate to plain postgres as soon as possible, so I could move production workloads to our standard setup.

My ideal setup would be one postgres instance which I can install myself from plain docker library image; one golang binary which embeds everything supabase offers turned off but with some envs to enable and that's about it.

Re: We are moving to General Availability

#79

Post by owenversteeg »

Supabase is great - I use them now and they and would be my choice for a new project today - but I have to say I am not a huge fan of how they communicated the whole auth-helpers and ssr situation, and I am not the only one with this comment by a long shot. This is, I think, a part of wider issues with their documentation; it seems like whoever's doing documentation at Supabase is intelligent but stretched thin. Particularly for Sveltekit, the documentation and examples are incomplete, there isn't any guide to migration or how to modify your code, and if you Google things or follow any links or examples you quickly end up in a web of deprecated repositories where it's unclear what to do next or replace them with. One example: https://github.com/supabase-community/auth-ui

If you produce a product for developers, you really need to have 1) quality, readable documentation with an introduction that noobs and pros alike can follow, 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries, 3) obvious migration guides and timelines whenever you deprecate something. Supabase lacks all three, which is extremely frustrating and means there's always a giant caveat when I recommend them. They're still the best, it's a very powerful and impressive product, and the possibility of self-hosting is amazing.

Re: We are moving to General Availability

#80

Post by spencerchubb »

Jabbles wrote: post #76
kiwicopple wrote: post #2

hey hn, supabase ceo here we just announced GA, after ~4 years of beta. for those who don't know: supabase is a postgres hosting company. we also host other open source "backend" tools that make it easy to get started with postgres (tools like PostgREST for auto-generate APIs [0]) we owe a lot to the HN community. you launched us 4 years ago [1], when we were just a few developers. since then HN has been a staple in…

Why do you not use capital letters in the typical way?

capital letters are atypical in many internet circles, particularly younger. so maybe it's a habit from frequenting those circles or a deliberate branding choice
Post reply on HN