Step 22: instance config decided as ~/.werkator.yml, open questions sharpened
Host/instance configuration (domain, port, registry, global concurrency) lives in a .werkator.yml in the home directory of the user running the instance — one instance per OS user, matching the platform model; repo configuration stays in each repository's .git/werkator/. Repo-level instance keys get ignored with a warning once a home config exists. The open questions now name the decisions still needed: repo defaults in the home file, cwd-vs-registry precedence, repo naming, and whether the third .werkator.yml location should carry a distinct name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
a8df7cc9d4
commit
da1054bf90
@@ -170,4 +170,4 @@ The build image grew into one fat trixie rootfs (JDK 21 headless + Go + Node/npm
|
||||
|
||||
- Session C: `BwrapBuildRunner` delegates to the `werkdock` CLI.
|
||||
- Session D: the webspace install path replaces the self-build prototype in `tools/remote`, untangling the builder-vs-built roles.
|
||||
- Multi-repository support for one Werkator instance (planned as step 22, whose plan document rides along in this PR).
|
||||
- Multi-repository support for one Werkator instance (step 22, planned on branch `22-multi-repo`).
|
||||
|
||||
Reference in New Issue
Block a user