docs(ops): log in with personal SSH keys, not the CI deploy keys #339
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!339
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/ssh-access-personal-keys"
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?
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_KEYandBROUTER_DEPLOY_SSH_KEY.What changed
docs/deployment.md: the host table and the emergency section usessh root@trails.coolandssh -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 nametrails.cool, not the IP, so that an entry in~/.ssh/configcan 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