Compose edit & deploy¶
Opening the editor¶
From a project’s ⋯ menu on the Docker page:
| Action | What you get |
|---|---|
| Quick edit | In-page modal (textarea) for compose and optional Dockerfile tab |
| Full editor… | Dedicated multi-file page: syntax highlighting, versions/drafts, validate YAML |
From Quick edit, use Open full editor → (or the Dockerfile equivalent when that tab is active) to leave the modal for the full page.
Desktop
Prefer Full editor… from the ⋯ menu when you need history, drafts, or multi-file tabs. Quick edit is best for small one-off edits.
Multi-file projects¶
On Docker → Full editor, PiHerder loads when present:
docker-compose.yml(or compose.yaml)- override file
.envDockerfile
Tabs edit each file (file badges in the chrome); Save & Deploy writes the full set and redeploys. Version history stores multi-file snapshots (merge-on-save so one file no longer wipes the others).
Word wrap: toggle wrap in the editor. Line numbers stay aligned with wrapped lines (gutter heights remeasured after the overlay is forced to the editor size).
On the host, Compose still auto-loads override + .env in the project directory.
Check updates vs Deploy¶
| Button | Effect |
|---|---|
| Check updates | Pull / image compare — no up -d. Runs as a Job (docker_stack_check) with live log. |
| Deploy | Pull + up -d. Runs as a Job (docker_stack_deploy) with live log; pending-update badge cleared on success. |
Both actions open the job holding modal (same pattern as OS/container patch). Follow progress under Jobs or Audit if you leave the page. Only one stack check and one stack deploy run at a time per host.
New project wizard¶
Creates a project directory under the Docker base dir and optional initial compose.
Template stacks¶
If a project is template-managed, prefer the deployment / redeploy flow. Full compose edit is intentionally gated so desired state stays authoritative. The ⋯ menu labels advanced raw edit clearly.