3.1 KiB
3.1 KiB
Infrastructure current state
Last audit: 2026-10-11. Source: read-only SSH session as codex, local
repository inspection, and Gitea API. This document separates measured facts
from planned configuration.
VPS facts
- Host:
avprogs.hlab.kz,206.223.249.118, SSH port22, usercodex. - OS/kernel: Ubuntu Server
24.04.5 LTS,6.8.0-142-generic. - Resources: 4 vCPU, 7.7 GiB RAM, 3.8 GiB swap, 99 GiB disk with 93 GiB free.
- Network: interface
ens3, IPv4206.223.249.118/32. codexis UID/GID 1000, groupscodexandusers; non-interactive sudo is unavailable.- SSH service is running. The inspected sshd configuration has public-key and
password authentication enabled and
PermitRootLogin yes; no SSH changes were made. - Docker, Docker Compose, Git, Nginx, Caddy, Certbot, application paths, and application services are absent. Only base OS services and SSH were running.
- Public listeners observed: TCP
22; local resolver listeners on loopback. - UFW is reported active in the supplied VPS notes, but the audit account could not independently read its status. Treat firewall state and rules as unverified.
Application and Gitea facts
- Repository:
admin/akyldash, default branchmain; Gitea version1.25.5. - The repository API reports push permission, Actions and packages enabled, and
PRs enabled.
mainis protected and requires one approval; the current API principal cannot push or merge directly tomain. - The Gitea token lacks
read:userandread:package; runner status and package publishing permissions could not be checked. No workflow existed at audit. - Production Compose describes Python Search API
0.11.3, SQLite account and review data, and OpenSearch3.7.0withanalysis-icu. Nothing is running. - Compose binds the API to
127.0.0.1:8080, leaves OpenSearch private, uses a named OpenSearch volume, and a host data bind mount. TLS/reverse proxy, registry digest deployment, backup, rollback helper, and systemd deployment are not configured. - The app has no migration framework or SMTP setup. Current app versions:
backend
0.11.3, frontend0.1.2, Telegram bot0.2.2(the bot is not deployed on this VPS).
Checks not completed
- SSH completed with the user config explicitly selected; plain SSH was blocked by permissions on a system config include. The private key was not read.
- UFW rules require root and remain unverified.
- DNS delegation, HTTPS, Cloudflare Full (strict), public application health, Actions runner availability, registry publishing, and production deployment have not been tested.
- No packages or services were installed or changed on the VPS.
Next owner actions
- Review and run the root bootstrap on the dedicated host.
- Review SSH/password/root policy and firewall rules separately; this change did not touch them.
- Set up DNS, origin certificate, reverse proxy, protected secret files, and initial corpus/index.
- Confirm a Gitea Actions runner and package permissions, then test CI and backup/restore before considering automated production deploy.