branderson
0994b24347
The setup said to copy docker-compose.yml to docker-compose.override.yml, edit that, and then run a bare `docker compose up -d`. That is wrong twice. `docker compose up` reads docker-compose.yml AND docker-compose.override.yml, and merges them - so an override leaves the example values in play rather than replacing them. And a committed docker-compose.yml means a bare `up` in a fresh clone starts the guard pointed at example.invalid, doing nothing useful and reporting a devbox unreachable that was never configured. It is docker-compose.example.yml now, copied to docker-compose.yml, which is gitignored - the same shape as etc/config.example, and the place a host and some URLs belong. The example also will not start as shipped: its host is CHANGE-ME.example. invalid and the guard refuses that. dejima's nginx example takes the same approach for the same reason - a file that cannot become a live config by being copied and forgotten. The refusal names the value rather than saying the host is unreachable, because unreachable is what it would otherwise look like. Three tests: the placeholder is refused, the shipped example still carries it, and no docker-compose.yml is committed. The second exists because the first stops protecting anything the moment somebody puts a plausible hostname in the example. `bats test/` 23 passing.
5 lines
62 B
Plaintext
5 lines
62 B
Plaintext
secrets/
|
|
docker-compose.yml
|
|
docker-compose.override.yml
|
|
*.swp
|