2.9 KiB
2.9 KiB
Infrastructure access
Discover existing access first
In a new Codex session, inspect the SSH alias and key file metadata without printing key contents, then check the connection:
ssh -F ~/.ssh/config -G akyldash_vps | awk '$1 == "hostname" || $1 == "user" || $1 == "port" || $1 == "identityfile" { print }'
test -r ~/.ssh/akyldash_codex && echo 'SSH key is available'
ssh -F ~/.ssh/config -o BatchMode=yes akyldash_vps 'id; hostname'
gitea-api GET /version
gitea-api GET /repos/admin/akyldash
Do not ask for the host, login, password, token, or key again before these checks. Never print a private key, token, or complete environment file.
VPS
- SSH alias:
akyldash_vps, usercodex, host206.223.249.118, port22. - SSH configuration:
~/.ssh/config. - Identity file:
~/.ssh/akyldash_codex(path only; never copy its contents). codexcan run unprivileged read-only diagnostics. The audited account has no non-interactive sudo and must not be added tosudoor thedockergroup.- Host package installation, service setup, firewall changes, secret creation, backup restore, and production changes require the VPS owner to run a reviewed root command. No restricted deploy-helper is installed yet.
- Never connect to other VPS hosts or Synology as part of this deployment.
This execution environment's system SSH config include had unsafe file
permissions, so plain ssh akyldash_vps failed. ssh -F ~/.ssh/config ...
worked. Network policy may also require an approved SSH command. If the key is
missing in a future execution environment, report that limitation; do not
retrieve it from another machine.
Gitea
- Repository:
https://git.vakanaut.ru/admin/akyldash. - Use the installed
gitea-apihelper; it reads credentials from the environment. Never inspect local credential files, print environment values, or construct HTTP authorization headers. - The audited API token can read/write this repository and create issues, but
does not have
read:userorread:package. An API403caused by a missing scope is not evidence that the account itself lacks the permission. - Protected
mainrequires one approval. Do not push directly tomain, merge automatically, or start a review. Work on a feature branch and use a PR. - Gitea Actions and package features are enabled for the repository, but runner availability and package publishing permissions have not been confirmed.
Who can do what
| Role | Operations |
|---|---|
codex over SSH |
Read-only host diagnostics; inspect service health and public listeners |
| Restricted deploy-helper | Intended future allowlisted backup/deploy/status actions; not installed |
| VPS owner/root | Bootstrap, package installation, SSH/firewall, secret setup, recovery, and approval of production changes |
| Gitea repository writer | Feature branch push and PR creation; protected-main merge needs an approval |