Compose prefers the shell environment over the env file, so with
CODEMAN_APPDATA_PATH or CODEMAN_PORT preset, a different typed answer went into
docker/.env and the summary while the stack ran on the preset: state split
across two folders and the next plain start mounted another home. Setup now
unsets everything it wrote, so the file it just printed is what Compose reads.
The test stub honours that precedence, and the questions get their first test
through a real pty.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`docker info --format` exits 0 with the daemon unreachable on those clients,
so a user outside the docker group got a raw Compose error and a "network
hiccup" hint after docker/.env and the data folder had already been written.
`docker version --format` exits 1 on every release and keeps the same stderr
text, so the permission branch still matches. The test stub now answers `info`
the way those clients do.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new Docker install was: clone (undocumented), copy .env.example by hand,
fix an Unraid data path and a Perth time zone, replace `changeme`, run the
start script, and then guess when the server was up. Start-Codeman.sh now
does all of it from a fresh clone:
- Preflight names the fix for a missing docker CLI, a missing or too-old
Compose plugin (config --environment needs 2.27.2, docker/compose#11891),
and an unreachable daemon (docker group, never sudo).
- With no docker/.env, it asks three questions (data folder, port,
password; Enter takes each default: ~/codeman-docker, 3000 or the next
free port, a generated password) and writes docker/.env FROM the example,
so every key the updater's diffRequiredEnvKeys expects is present. Mode
0600, host time zone, values Compose would interpolate single-quoted.
Refuses $HOME, ~/.codeman (a native install's state dir) and anything
inside the checkout (the image build context). --yes / no TTY take the
defaults, --setup-only stops after writing the file. An existing .env is
never edited, and root never runs the setup (Unraid keeps the hand route).
- After `up`, it waits until the server answers (docker exec probe, crash
loop caught by the restart count) and prints the URL, the LAN URL, the
generated password and the logs/stop commands; --no-wait skips the wait.
- `changeme` is refused before anything starts (the container publishes on
every interface and holds the Docker socket); Update-Codeman.sh checks it
before its build and down so the stack is never left stopped.
- Compose settings are read with ONE config --environment call, with its
error reported, instead of three silent ones.
docker-compose.yaml and server.Dockerfile are untouched (their hashes gate
the in-app updater), and .env.example changes values and comments only.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>