CI: auto-deploy release to kai-server after publish #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-04-28T07:26:44Z - https://github.com/coilysiren/eco-telemetry/issues/4
release.ymlpublishes the GH release zip but doesn't install it on kai-server. Today the install flow is manual:coily ssh deploy eco-mod EcoTelemetryfrom a laptop, which fast-forwardsinfrastructureand runsinstall-eco-mod.sh EcoTelemetry.Goal: after
release.ymlpublishes, automatically run the install on kai-server, then restarteco-server.serviceso the new DLL loads.Design notes:
bash ~/projects/coilysiren/infrastructure/scripts/install-eco-mod.sh EcoTelemetry. Files land under kai-owned paths, no sudo. Followed bysudo systemctl restart eco-server(sudo needed - either NOPASSWD entry for that specific systemctl call, or use the existingcoily ssh deploysudo-piping pattern).tailscale/github-action@v3(same shape as canonical k3s deploy). Then sshkai@100.69.164.66(tailnet IP)..pubto/home/kai/.ssh/authorized_keys, store private in SSM under/eco-telemetry/deploy-ssh-key, sync to GH secretDEPLOY_SSH_KEY. Restrict key inauthorized_keyswithcommand=to only allow the install script + restart, so a leak doesn't grant general shell./etc/sudoers.d/kai-eco-server-restartgrantingkaiNOPASSWD on/usr/bin/systemctl restart eco-serveronly.Once that's in place, the contract is: push to main -> release publishes -> kai-server pulls + restarts -> Eco loads new mod.