Let deploy-bot's SSH key work from the new runner box #33
Loading…
Reference in a new issue
No description provided.
Delete branch "armin-bot/impress:claude/runner-box"
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?
The Forgejo Actions runner is moving off code.openneo.net onto its own machine, runner.openneo.net (
74.207.234.34). See OpenNeo/openneo-code#5 for the why and the full rollout.deploy-bot's SSH key only works from the runner's IP, so this lets it work from the new box too.Changes
deploy_bot_allowed_ipbecomes a list,deploy_bot_allowed_ips, joined intoauthorized_keys'sfrom="…". During the move it lists both the old (45.79.220.14) and new (74.207.234.34) runner IPs, so deploys keep working whichever machine runs them. IPv4 only: job containers have no IPv6.docs/deployment-setup.mdand aci.ymlcomment now say where the runner lives.Rollout
bin/deploy:setupfrom this branch, then merge.45.79.220.14and runsbin/deploy:setupagain.Testing
ansible-playbook --syntax-check deploy/setup.ymlpasses, and the line renders asfrom="45.79.220.14,74.207.234.34",….known_hostsis for impress.openneo.net, and production's firewall has no rules for the runner's IP.🤖 Generated with Claude Code
https://claude.ai/code/session_014PWWd1c4UFRKce9t7XXiaP
WIP: Let deploy-bot's SSH key work from the new runner boxto Let deploy-bot's SSH key work from the new runner box