-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Stuck after setting up Supabase when using "Deploy Now" #298
Comments
same issue here. |
@leerob @thorwebdev this looks like a breaking bug that I'm not sure how to address, as it arises from interface with Vercel platform. |
For anyone still stuck with this issue. I have avoided it by deploying directly from the Vercel Templates page: Also, I chose a different region. Singapore in my case. |
I had this same problem but I think I have a solution. Do you think that is the reason? |
Interesting. I didn't even realize that option existed. I think that's new,
and it does sound like it's probably what's breaking things.
…On Wed, May 1, 2024, 10:45 PM Tristan Rhodes ***@***.***> wrote:
I had this same problem but I think I have a solution.
The second time I tried the Deploy button and created a new Supabase
project, I unselected the "add random seed data" button.
After that, the deployment was completed successfully.
Do you think that is the reason?
Perhaps the deploy process doesn't like when Supabase preseeds the
database with tables and data?
—
Reply to this email directly, view it on GitHub
<#298 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASCYPGJKBYIUVUITOREPK6LZAGSDVAVCNFSM6AAAAABDME4Z7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZGQZTINRTGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I tried to deploy a new project using the Deploy Now button and the process got stuck after completing the Supabase setup.
Additional feedback, which would have helped error recovery retrying by clicking "Deploy Now":
Currently, my projects are created in Vercel and Supabase, and I need to continue manually, using the information in the README.
The text was updated successfully, but these errors were encountered: