-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Suggest a directory for the compose file in the documentation #7708
Comments
Nah I don't think so. I think people are smart enough to think about this themselves. |
I still think it would be a good idea to suggest a path, or use |
Not a bad idea, I missed that one. Check out the Docker file, what do you think? |
It works as expected. Container names should be consistent now. |
Hi there! This is an automatic reply. This issue is now 🔒 closed. Please be aware that closed issues are not watched.
Thank you for your contributions. |
Support guidelines
Description
Please provide a suggested directory to save the docker compose file(s) into, because the name of the directory becomes part of the docker container name. The name might be used in scripts like the script that is recommend in the backup page.
Different docker container names makes confusion like here and here
Solution
Edit the docs. Provide an example path for the docker compose file(s) so that it is assumed to be the default and consistent path between different installations. I personally suggest:
~/docker/firefly-iii
What are alternatives?
Use the
container_name
key in the docker compose file (reference)Additional context
No response
The text was updated successfully, but these errors were encountered: