Arnaud Morvan

There are multiple way to set the project name: https://docs.docker.com/compose/project-name/ I'm used to add a `.env` file: ``` COMPOSE_PROJECT_NAME=georchestra ``` No need to set it on command line on each...

If I understood correctly, pretty sure yes, it will resolve this issue. BTW `geochestra` or `georchestra-dev` would be more meaningful than `docker` in this case.

Yes, so be careful that when upgrading some customer projects, if might change compose project name.

I may miss something : - it seems **not a big issue** to loose some volumes in **dev** on such change - but it could be a bigger issue to...

Yes but be careful that some production repositories are forks of this ones, subjects to merge on upgrades. As I said, in most cases those volumes might be overridden using...