Repository navigation
Layout of a whole project with multiple services? #167
Unanswered
Matthias529
asked this question in
Q&A
Replies: 1 comment 5 replies
|
Dockman runs compose up with --remove-orphans, this will remove any service no longer part of the compose file and are still running There is no way to change this. What is the reason for having separate files for the related services, I would reccomend combining related services into a single file. The reccomended file system was left over from v2 where dockman had some limitations on the filesystem. It is no longer the case. Use whatever structure you want. |
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, first of all, thank you for a great product, that's really easy to use and deploy.
How would I go about structuring a compose project out of multiple services which I want to be able to start/stop and re-deploy separately? On my previous docker engine on my nas, I had separate compose.yml files for each service, but the tag "name: media-compose-project" in each of those and docker-compose would link it all under one project. When I try this in dockman, it shuts down running services of the project if I (re)deploy the next one.
PS The link under "See also: Recommended file layout for best practices." in the documentation is broken, thus no best practices ;-)
All reactions