# Infrastructure access ## Discover existing access first For repository work in Windows Codex, use `commerce-infra` to read the `commerce/akyldash` context through Gitea Infrastructure Registry MCP. Use Gitea Codex MCP to read the project sources and prepare changes. Use the repository PR rules for formal review and permitted merge. Host access is needed only for separately authorized runtime diagnostics. Check the configured SSH alias and key metadata without reading key contents. Do not request passwords, tokens, or keys, or print a complete environment file. ## VPS - SSH alias: `akyldash_vps`, user `codex`, host `206.223.249.118`, port `22`. - SSH configuration: `~/.ssh/config`. - Identity file: `~/.ssh/akyldash_codex` (path only; never copy its contents). - `codex` can run unprivileged read-only diagnostics. It has no sudo or Docker group membership; Docker CLI access to the daemon is denied. Do not add it to either group. - Bootstrap is complete. Docker and Compose are active, but no root-owned repository checkout or restricted helper is installed yet. The owner can run `infra/bootstrap/audit-host.sh` from the reviewed root-owned checkout to report Docker containers/volumes, protected-file metadata, UFW rules, ports, and ISPmanager status without showing secret contents or changing state. - Host package/service configuration, firewall changes, protected env/secret creation, backup creation, recovery apply, and production deployment require a reviewed owner/root command. `infra/deploy/install-helper.sh` grants the fixed verifier, read-only Compose `config`/`status`, and guarded rollback commands. It does not grant general sudo or Docker access; it is not installed on the VPS. - `infra/deploy/prepare-production-config.sh` is an owner-run root operation. It refuses to overwrite existing files, copies only the tracked env example, generates a random review secret, and writes both files with mode `0600`. It does not start Compose or create volumes. - Never connect to other VPS hosts or Synology as part of this deployment. For authorized runtime diagnostics, use the configured read-only SSH access. Validate the resolved alias, hostname, user and port before connecting. Only use an existing approved key for this environment. If access is unavailable, record the limitation. Do not copy keys between environments. ## Gitea - Repository: `https://git.vakanaut.ru/admin/akyldash`. - Use Gitea Codex MCP to read the repository, prepare changes in a separate branch and open the PR. Use Gitea Agent MCP for formal review, approval and permitted merge according to [AGENTS.md](../../AGENTS.md#согласование-изменений). Do not inspect credential files, print secret environment values, or construct authorization headers. - Protected `main` requires at least one independent approval and the required CI checks. Direct push to `main` is prohibited. Merge requires the current head approval and the checks listed in AGENTS.md. - A `403` can indicate missing scope or owner permissions. It does not establish runner absence. Only a repository owner may obtain the repository runner registration token in `admin/akyldash` Settings → Actions → Runners. Do not use organization or instance tokens or put the token in Git, a command argument, or a report. See [CI_RUNNER.md](CI_RUNNER.md). ## Who can do what | Role | Operations | |---|---| | `codex` over SSH | Unprivileged diagnostics; Docker daemon, UFW rules, and protected paths require the root audit script | | Restricted helpers | Read-only drift check and Compose `config`/`status`, plus guarded rollback; not installed on the audited VPS | | Restricted rollback helper | Can restore prior local backend/OpenSearch images from a verified backup after an explicit data-compatibility confirmation; not installed on the audited VPS | | 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 |