-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
Unable to use an existing Supabase connection/DB #4922
Comments
Same issue for me |
1 similar comment
Same issue for me |
Same issue here - I am looking for the ability to use my existing supabase db instance instead of creating the completely new |
bolt asks to create a new database, which I have already created in supabase (project fork) |
@EricSimons can you help us? I have a project that has already cost me 55M tokens and I can't connect to an existing database so bolt can create tables etc. (in my case after a fork of the project to save tokens) |
Describe the bug
Unable to establish a connection from bolt.new with existing database in Supabase even after updating URLs in
.env
Bolt.new frequently loses connection to Supabase, resulting in the creation of a new database instance. This issue requires re-creating tables, views, and other database structures repeatedly, significantly increasing development time. It needs to be resolved.
Link to the Bolt URL that caused the error
https://bolt.new/~/github-advheypm
Validations
Steps to reproduce
Step1 : Click to Connect to Supabse
Step 2: "No, Use Existing Database"
Expected behavior
By clicking on "No, Use Existing Database" button, bolt.new should be able to use existing DB.
Screen Recording / Screenshot
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: