# Status: ino VPS server - Gate 1 — Product: APPROVED 2026-10-09 - Gate 2 — Architecture: APPROVED 2026-10-09 - Gate 3 — Program Design: APPROVED 2026-10-09 - Gate 4 — Slice plan: APPROVED 2026-10-09 ## Slices - [x] Slice 1 — server tracer: bootstrap the Actix service through Once and verify health plus an authenticated stub API route through the proxy (local validation) - [x] Slice 2 — read API: list real Once apps with refreshed, redacted summaries (local validation) - [x] Slice 3 — remote deploy: deploy registry images with Once settings through the API (local validation) - [x] Slice 4 — update and self-update: safely update apps and preserve server runtime configuration during replacement (local validation) - [x] Slice 5 — release handoff: opt in from image metadata and update the selected app after publishing a release (local validation) - [x] Slice 6 — lifecycle and removal: start, stop, restart, and safely remove apps (local validation) - [x] Slice 7 — exec and logs: add bounded non-interactive command and log responses (local validation) - [x] Slice 8 — release readiness: complete safeguards, compatibility checks, documentation, and end-to-end validation (local validation) ## Notes for a fresh session - The user wants a server-side ino that remotely controls apps on their VPS through a JSON API, so they can also build their own management tool. - The default ino release flow should keep building and pushing the image to its registry. If deployment metadata is configured for the image, ino should then call the Once service on the VPS to update the selected app to the new version; this is not a Docker archive upload to the VPS. - The Once server runs on the VPS and uses the existing Once abstractions. Release-client credentials should be supplied outside the built image; image metadata may opt in and identify the target. - Proposed server configuration uses `INO_API_KEY` for the shared bearer credential and `PORT` for the server container port (default 80), binding to `0.0.0.0` by default. - The proposed API includes app list/deploy/start/stop/restart/update/remove, command execution, and logs. - Gates 1–4 are approved. The server uses an Actix Web adapter and runs as a Once-managed app container, bootstrapped by local-only, idempotent `ino once server setup`; it defaults to `silenloc/ino` and the running CLI version, with selectable `--version`. The root `Dockerfile` declares `LABEL remote="silenloc/ino"`; startup reconciles its route through the existing Once/Kamal proxy. `PORT` defaults to 80. - Gate 4 is approved with local validation. Slices 1–8 are complete locally: Actix server/API routes, Once-backed app list/deploy/update/lifecycle/exec/logs, self-update handoff, local fake-server release-client tests, output/request limits, docs, and image build. Docker-backed namespace-reader validation and local proxy tests passed. Temporary server/app containers, routes, volumes, and registry containers were removed; the existing proxy remains running. No public Ino image registry push, Git release push, or VPS deployment was performed because no deployment credentials or target were provided.