Commit Graph

4 Commits

Author SHA1 Message Date
698173c79d fix: copy the docker buildx plugin so nixpacks builds actually work
All checks were successful
CI / test (push) Successful in 48s
nixpacks shells out to `docker build`, which defaults to BuildKit;
without the buildx CLI plugin every build failed outright.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 04:31:55 +02:00
223b1ab8eb fix: enable git-over-ssh cloning for private repo installs
All checks were successful
CI / test (push) Successful in 32s
The manager image had git but not openssh-client, so ssh:// clones
failed outright ("cannot run ssh"). Install openssh-client, and mount
an SSH_DIR (key + known_hosts) into the container read-only so private
repos can actually authenticate — confirmed both gaps while deploying
against real private Zenvairo repos.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 04:27:49 +02:00
06d43f4ed8 fix: install nixpacks from its pinned GitHub release instead of ghcr.io image
Some checks failed
CI / test (push) Has been cancelled
ghcr.io/railwayapp/nixpacks no longer ships the nixpacks CLI binary at
/usr/bin/nixpacks (the image was repurposed upstream for something
else — confirmed while deploying to production, build failed with
"not found" for the pinned 1.41.0 tag). Download the exact release
tarball from GitHub instead, still pinned to the same version.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 04:22:02 +02:00
b8f5d8253f feat: SQLite-backed installations, REST API, admin auth and web UI
Replaces the slice-2 hardcoded installation with a full install/deploy
pipeline:

- SQLite persistence (better-sqlite3) with a single `installations`
  table and a draft -> cloning -> building -> built -> starting ->
  running/error/stopped state machine; env vars and bearer tokens are
  encrypted at rest (AES-256-GCM, key derived from MASTER_KEY).
- Build/run orchestration: git clone (+ .env.example key detection),
  `nixpacks build` as a logged subprocess, dockerode container
  run/stop with forced host/port env vars and a TCP-connect health
  check before flipping an installation to "running".
- REST API (installations CRUD, build/deploy/redeploy, logs, token
  regeneration) behind single-operator session-cookie auth with a
  basic login lockout.
- Vite+React admin SPA: login, installation list, install wizard, and
  a detail page to configure env vars, trigger build/deploy/redeploy,
  view the build log, and copy the authenticated /mcp/<slug> URL.
- Dockerfile (multi-stage, pulls in nixpacks + the Docker CLI) and
  docker-compose.yml for production deployment.

Validated end-to-end against a real cloned repo: draft creation with
env-key detection, build, the error path on a failed health check, and
delete, all through the live API.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 01:42:06 +02:00