There is one "issue" I discovered today, that has to do with docker: basically, we have the docker-compose.yaml file, when you docker-compose up, it creates containers with names as in that file, but prefixes them with parent directory name.

Currently it's docker, which isn't very unique (I have other projects that have docker-compose.yaml in a docker directory) so it can cause conflicts:

https://docs.docker.com/compose/how-tos/project-name/

The solution is to add top-level name: gargantext, but since we use named volumes, such a change could reset your current config.

@anoe Do you use docker-compose on test etc instances? I guess for devs it's not that important.