Github, Supabase & Vercel: What am I missing?
So love that you can create an integration between your source, your hosting and Supabase. Gives us the possiblity to create clean feature environments. But I feel that there is still some parts missing / not mature enough or that I just don't have the known hoe to use this correctly. So i'm hoping someone here can help.
So Vercel deploys when there is an new branch. Say feature/a branch is published.
Supabase only deploys an branch environment when there is an pull request for feature/a branch
Supabase and Vercel sync env variables. But only Supabase production is synced to Vercel Production environments and there is no sync to preview environment variable unless there is an Supabase branch for feature/a
Resulting in an not working feature environment at the side of Vercel until you create an PR and Supabase deploys. Does anyone know how to fix this? Think there are couple of options:
So Vercel deploys when there is an new branch. Say feature/a branch is published.
Supabase only deploys an branch environment when there is an pull request for feature/a branch
Supabase and Vercel sync env variables. But only Supabase production is synced to Vercel Production environments and there is no sync to preview environment variable unless there is an Supabase branch for feature/a
Resulting in an not working feature environment at the side of Vercel until you create an PR and Supabase deploys. Does anyone know how to fix this? Think there are couple of options:
- Match Vercel to deploy when branch is published;
- Somehow make Vercel only deploy on PR (but could not find anything like this in the documentation);
- Worse case: sync production variable to preview env variable of Vercel untill there is an Supabase branch. But that would not be as nice as having an clean environment for each feature with only seed data to start;
