Open mhellmeier opened 3 years ago
Hi @mhellmeier ,
did you try to kill the existing containers and rebuild them? Maybe docker-compose kill && docker-compose build
will help before starting the container again. Judging by the logs seems like the container has the old value still.
Also it's worth mentioning that this repository is for development purposes only. If you'd like to self host our infrastructure please refer to: https://github.com/standardnotes/standalone and respective documentation: https://docs.standardnotes.com/self-hosting/getting-started
Thanks a lot for your quick feedback, @karolsojko .
After some debugging, I found another place where I missed replacing the value of the container. Aftward I was able to successfully change the name.
Nevertheless, it would be great to see a piece of meaningful information in the logs like "Couldn't find or connect to the database DB-NAME" instead of a looping exception.
The default
docker-compose.yml
file creates adb
container for the database. Currently it isn't possible to change the container- / hostname of thisdb
container.If I change the name from
db
tofoo
everywhere (in thedocker-compose.yml
and the.env
file), thesyncing-server-js
doesn't start and loops the following error log: