8.8 KiB
8.8 KiB
Infrastructure current state
Last audit: 2026-10-12. Source: read-only SSH session as codex, owner-reported
UFW state, local repository inspection, and Gitea API. Root-only Docker state,
UFW rule details, and protected file metadata remain unverified.
VPS facts
- Host:
avprogs.hlab.kz,206.223.249.118, SSH port22, usercodex. - OS: Ubuntu Server
24.04.5 LTS; kernel6.8.0-142-genericfrom the prior inventory audit. - Resources: 4 vCPU, 7.7 GiB RAM, 3.8 GiB swap, 99 GiB disk with 92 GiB free at this audit.
- Network: interface
ens3, IPv4206.223.249.118/32. codexis UID/GID 1000, groupscodexandusers;sudo -n truerequires a password. Docker CLI cannot access/var/run/docker.sockascodex.- SSH service is running. The inspected sshd configuration has public-key and
password authentication enabled and
PermitRootLogin yes; no SSH changes were made. - Bootstrap completed. Docker CE/CLI
29.9.0, Compose5.6.0, containerd2.4.1, and runc1.5.2are installed; package versions and active Docker service were independently checked. The Docker daemon API remains root-only. /etc/docker/daemon.jsonhas the expectedlocallog driver and10m/3rotation limits. Bootstrap paths exist with root ownership:/opt/akyldashmode0755,/etc/akyldashand/var/backups/akyldashmode0700, and/var/lib/akyldash/datamode0750./opt/akyldash/current, verifier/rollback binaries, and the sudoers file are absent.codexhas not received sudo or Docker-group access. Metadata for/etc/akyldash/production.envand/etc/akyldash/review_secretcould not be checked because/etc/akyldashis root-only.- TCP listeners observed: SSH
22and loopback DNS only; no listener on1500,80, or443. No ISPmanager package or service unit was found through the unprivileged checks; root can confirm with the audit script below. - Owner reports UFW is active and allows TCP
22,80,443, and1500. Rule details were not independently read; no firewall changes were made. - Additional read-only runner checks on 2026-10-12 confirmed
/is ext4 with about 92 GiB free at the prior audit,/usr/bin/dockerd-rootless.shexists, andgit.vakanaut.ruresolves to195.209.48.28. From the VPS,https://git.vakanaut.ru/api/v1/versionreturned Gitea1.25.5; runner registration and Gitea Actions protocol connectivity are not confirmed. akyldash.kgresolves to Cloudflare IPv4/IPv6 edge addresses. From the VPS, HTTP, HTTPS, and/reviewstill return Cloudflare521; origin TLS and Cloudflare Full (strict) are not verified.
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 repository runner-list API returns
403because this API principal is not the repository owner. The Actions task API currently reports no workflow runs; this does not establish runner availability. Runner inventory and package publishing permissions remain unverified. - No public application listener is observed on TCP
80/443. Docker container/volume state still requires the root audit. Repository Compose describes Caddy2.11.6pinned by digest, Python Search API0.11.3, SQLite account/review data, and OpenSearch3.7.0withanalysis-icu. - The target publishes only Caddy on TCP
80/443. Backend and Caddy share a proxy network; OpenSearch and backend share a separate internal network, and backend has no host port. Caddy certificate storage, OpenSearch, and application data use persistent volumes/bind mounts. - The root-owned repository checkout, production env/secret files, Compose volumes/containers, backup, verifier/rollback helpers, and application are not confirmed installed. TLS and registry digest deployment for backend/OpenSearch are not configured.
- The repository has a cold-backup archive/verification tool and a one-shot restore apply tool that requires a marked replacement host. Backup/restore tests use synthetic data; neither tool has run against production. The archive preflight permits a clean first deployment to skip backup, requires backup for existing persistent data even without containers, allows absent named volumes only in explicit corpus-only initial-deployment mode, and rejects inaccessible/ambiguous mounts and incomplete/running service containers. Initial deployment docs require a second verified backup after index and admin initialization.
- Recovery bootstrap has an explicit
--recovery-targetmode that refuses the inventoried production hostname/IP; its host-identity guard has shell tests. The mode has not been run on a VPS. - The repository defines a root-owned read-only verifier, Compose
configandstatushelper, guarded rollback helper, and installer with exact sudoers command rules. None is installed on the VPS. CI contains no production deployment job; starting/stopping services remains owner-run. - A repository-scoped official
act_runner0.2.13installation is prepared ininfra/runner/: rootless Docker underakyldash-runner, 15 GiB ext4 loop-backed image/workspace storage, capacity 1, per-job limits (2 CPU, 3 GiB RAM, 512 processes), account slice limits (2.5 CPU, 4 GiB RAM, 2048 tasks), rotated file logs, and a systemd health timer. Jobs use theakyldash-cilabel and do not receive the rootless or production Docker socket. The owner reports a partial runner installation: the 15 GiB ext4 loop-backed store is active on/dev/loop0after manually enabling and starting its mount unit when the installer stopped. Remaining components, repository registration, and Online state are unverified; this PR makes no VPS changes. - Gitea repository runner inventory could not be read by the current API
principal (403). The owner has not supplied runner state, and no runner
Online status or runner-hosted workflow is claimed. The manual
runner-smoke.yamlworkflow is prepared but has not run. - An isolated local Compose smoke test built backend/OpenSearch images,
reached healthy status for OpenSearch, backend, and Caddy, and returned HTTP
200 for
/reviewthrough Caddy. Its containers, networks, and volumes were removed afterward. This does not verify VPS startup, DNS, or public TLS. - 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
- Docker Engine version from the server API, container and volume inventory,
protected env/secret metadata, sudoers, and detailed UFW rules require root.
infra/bootstrap/audit-host.shis provided for an owner-run read-only audit. - The backup archive/restore tool was tested with synthetic local data; a backup and restore of real production data remain unverified because production is not deployed.
- Cloudflare edge response was checked; origin DNS target, origin certificate, Full (strict), runner registration/Online state, registry publishing, and production deployment have not been verified.
- This audit made no host changes. No package or service was installed by this audit; the owner performed the initial bootstrap beforehand.
Next owner actions
- Install the approved root-owned checkout after its PR is reviewed, then run
sudo bash /opt/akyldash/current/infra/bootstrap/audit-host.shand share the output. The script prints no secret values and does not mutate the host. - After reviewing the audit output and confirming the target files are absent,
run
sudo bash /opt/akyldash/current/infra/deploy/prepare-production-config.sh; it refuses to overwrite existing files. Set the approvedDATA_ROOTand place the approved corpus/index and Cloudflare origin configuration. Do not deploy until data/service state and the required backup path are reviewed. - Run
sudo bash /opt/akyldash/current/infra/deploy/install-helper.shafter reviewing the checkout; it grants only fixed verification, Composeconfig/status, and guarded rollback commands. - After PR review and root audit, run
sudo bash /opt/akyldash/current/infra/runner/install-runner.sh. In the repository Settings → Actions → Runners create a repository-level runner; enter the token only at the interactive registration prompt as documented in CI_RUNNER.md. Then enable the runner and health timer, confirm Online, and dispatch the smoke workflow. Production deployment remains manual and has no CI job. - Test backup/restore and rollback only with synthetic data in an isolated environment before any production deployment.