-
Notifications
You must be signed in to change notification settings - Fork 3
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
could not open extension control zhparser.control #1
Comments
would you like to try The supabase in this project is eject to docker folder. You may need to check whether supabase update its setup and cause this error. I would like to keep it ejected until supabase supoort workflow and RUM, zhparser extension. |
Here is my output after running output:
(says there is logs printed below but nothing shows up) |
Maybe you should create a clean db before running it. |
You can try the following step:
supabase init may have changed its configuration, you should check it. Supabase is missing some extensions use ejected supabase in docker folder. |
Hi. Cool project. Great work so far!
I am trying to get the app to run locally.
I've run "supabase start" in the root after running "supabase init". Works fine.
After, I do a migration to seed the DB:
npx prisma migrate dev --name init
I receive this error:
I am also running "docker-compose up" in a different terminal. Seems there is something wrong there as well as I get:
I have a feeling I am not running the docker stuff correctly for local development. Any suggestions?
The text was updated successfully, but these errors were encountered: