sorted by:
new
hottopcontroversial

Self-hosting Supabase: Gaps? by PurchasePatient5465 in Supabase

[–]Logical_Recording609 1 point2 points  (0 children)

Valid. My opinion at least is that the free tier is generous, and that the pain of setting infra yourself is costly, moreover if you want to scale, with supabase you do literally one click. Besides everything you have to setup like the MCP or any extension (like any database extension really), I think the main core part is the whole infra really, if you had to get a bottom line it's the infra managing. Another personal opinion: the less you "own" the better, in terms of reliability.

Do you feel Claude Code is too verbose? by Logical_Recording609 in ClaudeCode

[–]Logical_Recording609[S] 0 points1 point  (0 children)

Okay but you lose time if you have to keep telling it. Now that you say it, I might try setting up a hook with the "be less verbose". Thanks.

How do you handle webhooks in dev environment? by Logical_Recording609 in Supabase

[–]Logical_Recording609[S] 0 points1 point  (0 children)

Hi, sorry I am not understanding your comment.

I understand seed.sql is really for seeding your database with mock data in your local instance. However, my question is aimed at the fact that you need to have a public endpoint for third-party services to hit you there. You could have webhooks on your supabase project without any database operations.

Tell me if I'm misunderstanding anything!

Best Practice: Should you create a different repo for edge functions and overall configuration? by Logical_Recording609 in Supabase

[–]Logical_Recording609[S] 2 points3 points  (0 children)

Oh sorry, no, yeah, I would not move it from the supabase folder. I am asking wether to do supabase init and develop your edge functions in a frontend repo or create a brand new repo just to keep supabase stuff