Well, we don’t using swarm because it is only one root server and all things data related between containers, like pma and mariadb are handled internaly so that I am not in need of exposing port 3306 (for now).
The problem here is docker self, becuase they are not be able to implement a simple “include: service.yml” option, which would make it less dirty and all would smoothly be spletted into sperate files per service.
And after all, it is smth. like a playgorund for both of us, because we are also experimenting with docker before we are going with it into production mode
If you have any ideas how to clean it up or how we could exclude some services into gitlab over only one repro but with multiple CI/CD support (which is also not possible because it is also not implemented but smth. which should have been there since there first release).
If the mentioned problems weren’t there, it would be easier to solve some problems but for now, we must fallback to a structure like this one because some developers are to lazy to implement such important stuff and no, we are not going to implement any workarrounds on our side, since it’s not our fault/problem that such important functionality is missing.
And sorry for this little rage but since I am also a developer I listen to that, what is wished from the users/community and as long as the wish is possible and fine, it will get implemented. This should be a rule for every developer, if he wants to save his users/community. Hope, that this is understandable