Set COMPOSE_PROJECT_NAME when invoking docker-compose

[benjaoming]

Fixes readthedocs/readthedocs.org#9318

[benjaoming]

Reminder to update readthedocs/readthedocs.org#9319 after this is merged

[humitos]

I commented on readthedocs/readthedocs.org#9319 (comment) about how to solve this without introducing this change.

I prefer if we can read this automatically from the .env file so we can keep the current setup working together with corporate Docker instances.

[benjaoming]

Re:

I prefer if we can read this automatically from the .env file so we can keep the current setup working together with corporate Docker instances.

I'll make a check to see if/how this works, but did you notice that the patch does not propose to overwrite existing env variables?

DOCKER_COMPOSE_PROJECT_NAME = os.environ.get('COMPOSE_PROJECT_NAME', 'community')

[humitos]

Yes. It seems this PR is not required anymore now that #148 got merged.

[benjaoming]

Agreed - the .env file does not trump existing environment variables so this PR can never wort together with a .env 👍

I found a segment in the Compose docs that specifices that .env can be used both for container instance variables and any other configuration, so I suppose it means that COMPOSE_PROJECT_NAME is supposed to be an intentional part of .env (I previously read the docs as if it was not intended for comfiguring Compose itself).

The “.env” file

You can set default values for any environment variables referenced in the Compose file, or used to configure Compose, in an environment file named .env. The .env file path is as follows: