-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy error #341
Comments
anyone else with this error, supabase key, url are production only whereas the deployment was in preview therefore failure |
I am facing the same issue. I will work on this again tomorrow morning and will get back to you with a fix if I find it. |
The solution seems to be to create separate Supabase projects for staging and production environments, and use the relevant keys and url's from the staging environment. |
Ok but how can I sync that? I was hoping to not create a testing Supabase project since I can use local to develop. If I have to support preview on Vercel, is there a way to sync 2 project? |
I have used the deploy button from github, followed all steps, as soon as i change anything in the github repo it fails, didnt touch the api/webhooks folder, just some footer changes and removing readme, and public files related to it. It worked before i changed anything.
The text was updated successfully, but these errors were encountered: