fix(config): only the repository the instance deploys itself from may restart it #87

2026-10-01T14:04:35+02:00

mi commented

2026-10-01 14:04:35 +02:00

tools/remote repo-add installed Werkator's own builds.deploy (restartsInstance, unsandboxed) into werkcrappit on mih09. Its main@deploy ran on the host with werkcrappit's build command and would have restarted the instance on every green main.

Registry entries get selfDeploys; with a registry, restartsInstance is refused in every repository whose entry lacks it (repository not served, logged). At most one entry may say it.
init --apply repeats; fragments are merged in order.
tools/remote: WERKATOR_SELF_DEPLOY_CONFIG for the watched repository alone; repo-add refuses a shared fragment with restartsInstance; a failed fragment upload now aborts.
v1.26.0

Before merging: add selfDeploys: true to the werkator entry of ~/.werkator.yml on mih09, or the self-deployed v1.26.0 will not serve werkator.

PR-doc: docs/prs/2026-10-01-PR#87-self-deploy-only-from-its-repository.md

🤖 Generated with Claude Code

`tools/remote repo-add` installed Werkator's own `builds.deploy` (restartsInstance, unsandboxed) into werkcrappit on mih09. Its `main@deploy` ran on the host with werkcrappit's build command and would have restarted the instance on every green main. - Registry entries get `selfDeploys`; with a registry, `restartsInstance` is refused in every repository whose entry lacks it (repository not served, logged). At most one entry may say it. - `init --apply` repeats; fragments are merged in order. - `tools/remote`: `WERKATOR_SELF_DEPLOY_CONFIG` for the watched repository alone; `repo-add` refuses a shared fragment with `restartsInstance`; a failed fragment upload now aborts. - v1.26.0 **Before merging:** add `selfDeploys: true` to the `werkator` entry of `~/.werkator.yml` on mih09, or the self-deployed v1.26.0 will not serve `werkator`. PR-doc: `docs/prs/2026-10-01-PR#87-self-deploy-only-from-its-repository.md` 🤖 Generated with [Claude Code](https://claude.com/claude-code)

mi added 1 commit 2026-10-01 14:04:36 +02:00

fix(config): only the repository the instance deploys itself from may restart it (#87 )

werkator build succeeded after 02:56

Details

e697987537

tools/remote repo-add installed Werkator's own deploy block into werkcrappit,
whose main@deploy then ran unsandboxed on the host and would have restarted
the instance on every green main.

- registry entries get selfDeploys; with a registry, restartsInstance is
  refused in every repository whose entry lacks it (not served, logged)
- at most one entry may say selfDeploys
- init --apply repeats, fragments merged in order
- tools/remote: WERKATOR_SELF_DEPLOY_CONFIG for the watched repo alone;
  repo-add refuses a shared fragment with restartsInstance
- v1.26.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

mi merged commit dbb6d9e4be into main

2026-10-01 14:17:40 +02:00

mi deleted branch mihoe/self-deploy-only-from-its-repository

2026-10-01 14:17:40 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mi/werkator#87