@Krinkle reported a situation where:
- There's an MW_SCRIPT_PATH that happens to be set in the environment (for use with mw-docker-dev).
- docker-compose takes values from the environment in preference to those defined in .env
- In MediaWiki-Docker's docker-compose setup, we pass MW_SCRIPT_PATH to the installer, but hardcode /w a bunch of other places.
This situation should probably be reconciled. It probably requires some (hopefully minor) changes to dev-images/dockerfiles/stretch/install.sh, as well as (maybe trickier) the WORKDIR for several images.
I _think_ it seems like the path here should either be fully configurable, or just not give the illusion of configurability with MW_SCRIPT_PATH, but this might need more thought.