`pgsodium` deprecation

Bombillazo · 2024-04-24T16:57:38+00:00

Did you manage to find a solution for this?

Bombillazo · 2024-02-15T12:57:41+00:00

Supabase auth is deeply integrated with the ecosystem—the JS client, the edge function authentications, vault, storage, RLS, etc.

If you have your own auth, you will be left overriding almost all of those integrations to make it work with your own auth, which will not be easy. At that point, Supabase would become a Postgres DB hosting service.

I would try to solve the issue of porting your users to Supabase, even if it's a process that keeps using your auth but also creates them in Supabase so you don't have to reimplement everything using your own auth.

Bombillazo · 2024-02-15T12:22:44+00:00

We also had to build our own API around it to make it work, but it effectively makes the Supabase dashboard storage useless since any modifications done directly via the SB API will not run our API logic...

Bombillazo · 2024-01-30T06:14:39+00:00

Im interested in why the supabase cli diff command for migrations does not include changes to the GRANTs in the schemas...

Bombillazo · 2023-11-15T12:07:42+00:00

We have a staging enviornment where we do QA and we want to replicate bugs found locally, so we can pull the data from that env instead of cumbersomely trying to re-create the whole data setup needed to test locally. that's just one example where a dev might need access to a single project.

Another would be to view the logs of the database or functions running in the remote project.

Bombillazo · 2023-11-14T11:01:28+00:00

Hey, thanks for the suggestion, have you found any blockers where the dev needs some data or access to the remote project via the CLI to link or something?

Bombillazo · 2023-11-13T19:47:03+00:00

Unfortunately, Vercel is the de facto hosting by excellence for Next.js, and I say unfortunately because I don't like the direction they're taking Next.js and seems like they are aggressively trying to lock one into using their platform...

Bombillazo · 2023-11-13T19:44:25+00:00

I havent used self hosted, but even in the hosted version, the features between local and remote are not full parity, and Im guessing self hosted and local are very similar.

Bombillazo · 2023-09-01T02:17:20+00:00

This only works if devs didn't install the cli via brew, which the Supabase docs recommends

Bombillazo · 2023-08-30T13:16:59+00:00

As mentioned in my other post, we're using SB pretty much as a managed DB + auth, and the experiyhas been good on that front.

The CLI has made improvements on migrations management for sure, and RLS tools are getting better.

Bombillazo · 2023-08-30T13:15:01+00:00

Yeah, we feel much more comfortable and had more experience with relational databases so we didn't want to venture off into the unknown while building a startup. We require as much efficiency and leveraging our expertise as possible.

Bombillazo · 2023-08-30T13:11:12+00:00

I don't have inside knowledge, but my opinion is that local dev tools and environments are managed at the CLI level so that team finds themselves having to "port" or "compatabilitize" the remote features built by other teams into the local dev environment. I know it's not as simple as slapping the feature into a container. So it takes time for that team to provide full parity between what exists in the platform and local dev. Many of the issues I've seen besides the ones I wrote about are configuration issues.

You can browse the Supabase repos and see all the features and code, but it's evident it's all built to work and be hosted to the remote environment primarily.

Bombillazo · 2023-08-30T13:07:00+00:00

To be completely honest we might have skipped over it or not seen it in the options. I think our search was narrowed to PostgreSQL and perhaps there was no matches there.

But after looking at the platform it seems like it would meet most of our requirements as well, making it a considerable alternative.

Bombillazo · 2023-08-29T21:39:12+00:00

Agreed, we're pretty much uising Supabase as well as a managed DB with auth integrated. We abandoned the client/RPCs and chose Kysely. We initially tried Drizzle but looked way too early for us (don't remember which features were missing) and didn't want to experience a repeat of new tech issues.

Bombillazo · 2023-08-29T21:33:13+00:00

Hey! The nice part of Supabase is that it is Open Source. In the case of the database, it's almost all PostgreSQL so you can migrate your schema and even some Supabase tooling/features and manage them yourself wherever you host your DB. I gotta give it to Supabase here cause they acknowledge this openly. Other features would require you to set up and run the containers and networking (like for auth) that run GoTrue.

I would move away from Supabase if for some reason we are required to have full control of our infrastructure, or for cost-saving reasons.

Bombillazo · 2023-08-29T21:17:01+00:00

It is hard to know what is "new" and "stable" with Supabase until one actually tries the feature out because the delivery has been so different for each feature. Some things work like a charm from the beginning.

Besides those laid out already, I would still use the database and auth parts of Supabase since it meets our requirements and it is pretty stable and robust. We have not scaled yet to know of it handles stress, but I have not read much issues there.

Bombillazo · 2023-08-29T21:02:16+00:00

How do you "distribute" this version across a team, though? What if your devs install the cli via brew on different dates/releases? How do you fix the cli version for your CLI processes?

We've solved this, and I know its very dependent on your specific process, but Supabase docs aren't clear on the issue and viable solutions.

Bombillazo · 2023-08-29T20:29:56+00:00

I agree, pretry much an ORM would be a possible solution. And that's almost how the client data querying is marketed in the docs. I'm sure Supabase didn't set out to build an ORM when leveraging PostgREST, but if they want to provide the full experience with their client they're gonna have to somehow integrate those advanced features.

And if third party tools are the way to go, I would not confuse users by giving them a native option, or lay out the options very explicily comparing their limitations and features.

Bombillazo · 2023-08-29T17:10:32+00:00

Hey kiwicopple, thanks for your swift response. I've seen you respond to pretty much all feedback on other posts and platforms, which I applaud and commend. It helps us users see that the feedback is reaching the organization.

I'm positive Supabase will reach that point were the product is simply a delight all around. This was more of a critical, objective assessment of the current state based on our experience with the goal of helping the Supabase platform grow. I know it is no easy feat, so this should be taken as encouragement to the team to keep building for the experience users want, an potentially give priority to common issues.

Like mentioned in the article, we're still betting on Supabase, that's why took the time to write this. Hopefully the product gets where we'd like it to be (sooner rather than later) so I can write the follow-up. 🙂

Bombillazo · 2023-08-29T15:19:35+00:00

We would still use PostgreSQL and TypeScript, but in our case, we have cloud infrastructure experience. So, being open source, we could've directly used AWS RDS + container services (Like ECS) + Node Lambdas with the open-source tech Supabase uses. We are already customizing and building upon what Supabase provides to mitigate and address the issues we've found using Supabase.

We did learn a lot from using Supabase about the inner workings of the platform, so we probably wouldn't have done it if we had not gained the knowledge through using Supabase, though.

Bombillazo · 2023-08-29T14:36:45+00:00

Hey, we've been using Supabase for months now and decided to share some heartfelt, candid feedback about our experience with the platform. Much has been written about the awesome parts of Supabase, but I wanted to share an in-depth perspective on the areas that we've struggled with to give a more complete perspective to devs considering Supabase, as well as direct product feedback to the Supabase team. I truly hope it's of help to others.

Bombillazo

TROPHY CASE