Files
akyldash/docs/operations/CURRENT_STATE.md
T
agent 02cf4e6e95
CI / tests-and-images (pull_request) Has been cancelled
Expose drift verifier through a fixed sudo helper
2026-10-11 19:39:02 +03:00

4.8 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 port 22, user codex.
  • 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, IPv4 206.223.249.118/32.
  • codex is UID/GID 1000, groups codex and users; sudo -n true requires a password. The current WSL2 session verified the SSH alias using the explicit user config and approved read-only SSH execution.
  • 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; DNS listeners are limited to loopback (127.0.0.53 and 127.0.0.54).
  • 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.
  • akyldash.kg resolves to Cloudflare IPv4/IPv6 edge addresses from the VPS. Both HTTP and HTTPS return Cloudflare 521; the origin is currently unreachable through the proxy.

Application and Gitea facts

  • Repository: admin/akyldash, default branch main; Gitea version 1.25.5.
  • The repository API reports push permission, Actions and packages enabled, and PRs enabled. main is protected and requires one approval; the current API principal cannot push or merge directly to main.
  • The Gitea token lacks read:user and read:package; runner status and package publishing permissions could not be checked. This change adds .gitea/workflows/ci.yaml; PR #42's run remains Waiting to run at the last status check, so a compatible runner is not confirmed.
  • Nothing is running on the VPS. Repository Compose now describes Caddy 2.11.6 pinned by digest, Python Search API 0.11.3, SQLite account/review data, and OpenSearch 3.7.0 with analysis-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 the backend has no host port. Caddy certificate storage, OpenSearch, and application data use persistent volumes/bind mounts. TLS, registry digest deployment for backend/OpenSearch, backup, rollback helper, and systemd deployment are not configured on the host.
  • 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.
  • Recovery bootstrap has an explicit --recovery-target mode 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, rollback helper, and owner-run installer with exact sudoers command rules. None is installed on the VPS.
  • An isolated local Compose smoke test built the backend/OpenSearch images, reached healthy status for OpenSearch, backend, and Caddy, and returned HTTP 200 for /review through 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, frontend 0.1.2, Telegram bot 0.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.
  • 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.
  • The Cloudflare edge response was checked, but origin DNS configuration, Cloudflare Full (strict), certificate validity, 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

  1. Review and run the root bootstrap on the dedicated host.
  2. Review SSH/password/root policy and firewall rules separately; this change did not touch them.
  3. Set up DNS, origin certificate, reverse proxy, protected secret files, and initial corpus/index.
  4. Confirm a Gitea Actions runner and package permissions, then test CI and backup/restore before considering automated production deploy.