Some installations need to stay reachable by a native process on the
same host outside the manager's own proxy — e.g. a legacy nginx
location serving media/signed URLs for an app that also happens to be
an MCP server. Previously this required manually recreating the
container outside the manager's lifecycle (lost on the next
build/redeploy). publishHostPort makes it a real, persisted setting.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Needed to install third-party repos we don't control (e.g. the
upstream gitea.com/gitea/gitea-mcp project) where nixpacks detects a
working build but the wrong/no start command, and pushing a
nixpacks.toml to the source repo isn't an option. Passed through as
nixpacks' own --start-cmd flag.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Lets a client still using Basic Auth credentials (e.g. against the
previous nginx + htpasswd setup) keep working without switching to a
bearer token immediately. Bearer auth remains the default and the
only option when no Basic Auth credentials are configured.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Nixpacks moves an installation's image tag to the newly built image,
leaving the previous one dangling. buildInstallation now removes the
superseded image (best-effort, skipped if still referenced), and
removeInstallationContainer removes an installation's image when the
installation itself is deleted.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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>
