Does not fully respect COMPOSE_PROJECT_NAME / parent directory _must_ be called `central`

Various strange things happen with docker-compose if this repo is cloned to a folder which is _not_ called `central`.

Setting `COMPOSE_PROJECT_NAME` fixes some but not all of the problems.

I will try to document specific problems, and any fixes, here.

Start by cloning the repository into a directory not named `central`, then reproduce the docker-compose problems with and without `COMPOSE_PROJECT_NAME` set. Record each specific failure and trace it to the relevant compose configuration, documenting the fixes and verifying that the setup works under a different parent directory.

Written by the indexing model from the issue text.