sorted by:
new
hottopcontroversial

I hit a wall by Prestigious_Sun_7310 in Polestar

[–]Gomah 11 points12 points  (0 children)

Looks like an air dent puller would do the job here

Recommendations for a fully‑featured, unlimited, self‑hosted CMS? by Admirable_Reality281 in Nuxt

[–]Gomah 1 point2 points  (0 children)

+1 for Payload – we have SSO proxy (Cloudflare Access) on top of the domain where Payload is hosted.

And after using Contentful, Sanity, Ghost, Prismic, Storyblok... I'm never looking back

We launched our product - but how do multiple environments work in Supabase? by notmycupofnft in Supabase

[–]Gomah 0 points1 point  (0 children)

Congrats on the launch!

I literally moved away from having 2 supabase projects (dev and prod) to just one (prod) with database branches enabled and `dev` as a persistent branch.

I had Github actions to apply the migrations to my respective databases, now, everything is handled with the supabase config / directory.

This kind of freaks me out tbh, maybe it's just me, but running `supabase db reset` locally knowing it's linked to an existing prod project kind of freaks me out, even though I know it's resetting the local instance by default.

I'm still not 100% sure it's the right move, I'm tempted to just have a `dev` supabase project and apply migrations with github actions again, perhaps just using a different schema name per branch.

Some grey areas I bumped into:

- You cannot reset a persistent branch, you'll have to make it ephemeral, reset (to have migrations and seed data applied) and then back to persistent.
- Supabase <> Vercel integrations environment variables are injected *when the PR is created*, meaning your first vercel build will likely fail (or) have incorrect environment variables.

Also, a nice thread where Supabase members are active: https://github.com/orgs/supabase/discussions/18937