docs(ops): log in with personal SSH keys, not the CI deploy keys #339

Merged
ullrich merged 1 commit from docs/ssh-access-personal-keys into main 2026-11-15 23:02:02 +00:00
Owner

Why

Operators no longer keep a copy of the CI deploy keys on their machines. Each operator logs in with their own SSH key, and the deploy keys stay only in the Forgejo secrets DEPLOY_SSH_KEY and BROUTER_DEPLOY_SSH_KEY.

What changed

  • docs/deployment.md: the host table and the emergency section use ssh root@trails.cool and ssh -p 2232 trails@ullrich.is. A new paragraph explains that the deploy keys are for CI only.
  • CLAUDE.md: the "Server access" block and the staging debugging note use the new commands.
  • .claude/commands/deploy-status.md: the command uses the host name trails.cool, not the IP, so that an entry in ~/.ssh/config can select the key.

Docs only, no code change. The archived OpenSpec documents still name the old key files, as a record.

🤖 Generated with Claude Code

## Why Operators no longer keep a copy of the CI deploy keys on their machines. Each operator logs in with their own SSH key, and the deploy keys stay only in the Forgejo secrets `DEPLOY_SSH_KEY` and `BROUTER_DEPLOY_SSH_KEY`. ## What changed - `docs/deployment.md`: the host table and the emergency section use `ssh root@trails.cool` and `ssh -p 2232 trails@ullrich.is`. A new paragraph explains that the deploy keys are for CI only. - `CLAUDE.md`: the "Server access" block and the staging debugging note use the new commands. - `.claude/commands/deploy-status.md`: the command uses the host name `trails.cool`, not the IP, so that an entry in `~/.ssh/config` can select the key. Docs only, no code change. The archived OpenSpec documents still name the old key files, as a record. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs(ops): log in with personal SSH keys, not the CI deploy keys
All checks were successful
CI / Dockerfile Package Check (pull_request) Successful in 3s
CI / Security Scan (pull_request) Successful in 8s
CI / Visual Tests (pull_request) Successful in 38s
CI / Checks (pull_request) Successful in 54s
CI / Journal Image Smoke Test (pull_request) Successful in 55s
CI / E2E Tests (pull_request) Successful in 3m0s
CD Staging / Build & Push journal Image (pull_request) Has been skipped
CD Staging / Build & Push planner Image (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
Cancel superseded CI / Cancel in-flight CI (pull_request) Successful in 5s
CD Staging / Tear Down PR Preview (pull_request) Successful in 16s
bf5e310999
Operators no longer keep a copy of the deploy keys. The SSH commands in
the runbook, CLAUDE.md and the deploy-status command now rely on the
operator's own key and ~/.ssh/config.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ullrich deleted branch docs/ssh-access-personal-keys 2026-11-15 23:02:02 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
trails-cool/trails!339
No description provided.