-
Notifications
You must be signed in to change notification settings - Fork 103
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
Setup with external db not working (Composer errors) #155
Comments
In the docker-prod.yml you should remove the
See the example here: |
Also, check this comment for recent suggestion on getting remote DB password to work: |
@rustymyers For the password I'm still fiddeling around, as the docker compose command doesn't seeams to work for me even if I set both password variables.... my current env_prod.list
Console output:
The DB is accessable, as I can connect via mysql on cmd without problems.... |
Try cleaning everything out and starting fresh. |
Sadly no luck:
|
For completenes I just changed my db user to no password, and everything works fine, except for entering the Django-backend (CSRF check failed).... So seems like there's still a bit work to do..... |
Try |
Tried this, but doesn't work either:
For some reason openeats seems to don't use the password supplied.... Regarding the CSRF error, was my fault, if anyone is running into this in the future, try the option "ProxyPreserveHost On" in your revese proxy. |
It seems the code is looking for Is your password being changed by the shell? Do you have an |
If "No Password" is equal to "empty password" depends on the constraints set in the table (as far as my smal knowledg reaches). I already tried passwords with and without special chars (in my case "!"), so it doesn't seeams to affect the behavior... maybe the order of the variables is important to the parser? |
I created a new instance with a custom MYSQL_ROOT_PASSWORD:
This seems to work as expected and the database is created, as is the superuser. I don't know that this means much, but the error for connecting is still showing in my docker db container:
The web services are working, I can create a new recipe and log into the admin interface. I wonder if the issue isn't the database? #61 (comment) |
So for better traceback my full setup: OS: Software: Setup:
I hope that maybe helps to localize the issue. |
Well, the problem shows up when the external db hast to be populated with the initial data. Edit: Regarding the comment, I don't think so, as at the moment I'm running openeats with a db user without PW and everything works fine, no errors at all. |
Have you updated the At first I got
|
Yes, i did. In my log, the error is the same as posted above. Any command including a call to the DB ended in "Access denied" until I changed the user to not require a authentication. After this, I did the steps you mentioned with the migration, which worked as they should. |
Try updating your env_prod.list to use |
Wow...... Sorry for wasting your time by this stupid mistake.... Everthing works now as exspected after applying the migrations after the restart again -.- Thank you very much for your help! |
Sorry it took me so long to see that :) |
Hey,
I just tried to setup openeats on my server running an MariaDB.
After reading the setup guide and trying around I always get errors on running quick-setup.py
My files:
docker-prod.yml
docker-prod.override.yml
env_prod.list
Error reported by quick-setup.py:
Can someone tell me what else I have to change?
Thanks in advance!
The text was updated successfully, but these errors were encountered: