Skip to content

Fix managed Kimaki self-upgrades - #581

Merged
chubes4 merged 3 commits into
mainfrom
fix/580-kimaki-service-user-prefix
Sep 6, 2026
Merged

Fix managed Kimaki self-upgrades#581
chubes4 merged 3 commits into
mainfrom
fix/580-kimaki-service-user-prefix

Conversation

@chubes4

@chubes4 chubes4 commented Sep 6, 2026

Copy link
Copy Markdown
Member

Summary

  • install managed non-root Kimaki into a prefix owned by the configured service user
  • render systemd ExecStart, PATH, and npm_config_prefix against that writable installation
  • converge existing root-global/non-root-service installations without weakening permissions or adding sudo grants
  • preserve root-service, local, external WordPress, and multi-instance behavior

Fixes #580. Related to #203.

Verification

  • bash tests/kimaki-install-existing.sh (28 assertions)
  • bash tests/service-identity-adoption.sh (27 assertions)
  • bash tests/bridge-render.sh
  • bash -n bridges/kimaki.sh tests/kimaki-install-existing.sh tests/service-identity-adoption.sh
  • git diff --check
  • Homeboy audit: zero introduced findings

tests/service-migration.sh retains four pre-existing macOS fixture failures that reproduce unchanged on main; this change does not touch those paths.


AI assistance disclosure: xAI Grok 4.6 via OpenCode and Homeboy produced the initial candidate; GPT-5.6 Sol via OpenCode reviewed it, corrected identity/error handling and test isolation, and ran verification under Chris Huber direction.

@chubes4
chubes4 merged commit cfb52fb into main Sep 6, 2026
67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Install Kimaki into the managed service user prefix so self-upgrade works

1 participant