Tomas Dvorak
9e3aa3aa17
Phase 0 cleanup verified end-to-end:
- Delete vendored APwhy runtime (cmd/apwhy, internal/apwhy) and the
unwired copy (internal/api/server.go + static bundle + cloned
internal/{storage,analytics,auth,rbac}) — ~7.5k lines of dead code.
- Keep Containr's native internal/gateway; move APwhy management
routes under /api/v1/gateway/* so they stop colliding with the
native /services paths. Fix handlers against the real schema:
UUID ids via RETURNING, integer enabled flags, plan validation,
service validate endpoint, unique-violation mapping.
- Port agents.go off GORM onto sqlc (sqlc/queries/agents.sql);
drop gorm dependencies; fix sqlc schema drift (services.environment_id).
- Replace the SELECT 1 goose baseline with the real consolidated
schema (52 tables) minus APwhy's parallel auth/RBAC objects;
idempotent via IF NOT EXISTS / OR REPLACE / guarded DO blocks so it
replays cleanly over legacy installs. Add a drop migration for the
dead objects and delete the legacy filename-tracked migrations/
loader, directory, and Dockerfile copy. Verified via cmd/migrate:
fresh install 53 tables, legacy upgrade clean to 20260917000000.
- Canvas: add invisible React Flow handles to ServiceNode so inferred
auto-connections stop emitting warning #008.
- Remove reactflow dep (superseded by @xyflow/react), test harness
cmds, and legacy 0001_init.sql backups.
Authored By: TDvorak <[email protected]>
Containr
Self-hosted platform for deploying and managing containerized services. Railway-style project canvases on your own hardware.
Quick Start • Features • Architecture • Guides • Contributing
What is Containr?
Containr is an open-source control plane for Docker. It gives you a project-first deployment workflow — create a project, drop services onto a visual canvas, wire them together with environment variables, and deploy — without Kubernetes, without a cloud bill, and without giving up control of your infrastructure.
The UI is inspired by Railway's project canvas: services appear as nodes, connections are inferred automatically, and everything — logs, metrics, deployments, builds — is one click away.
Features
- Project canvas — visual service topology with groups, drag/drop layout, and auto-inferred connections
- Deployments — Docker-based deploys with history, logs, and rollback
- Git integration — deploy from GitHub, GitLab, Bitbucket, or Gitea; repository and branch pickers, webhooks, GitHub App support
- Builds — build pipeline with live status over WebSocket
- Service metrics — real CPU/memory/network telemetry from Docker stats
- Templates — one-click service catalog (databases, apps, tooling)
- Databases — managed database services with backup/restore actions
- Cron jobs — scheduled jobs with execution history
- Preview environments — per-project preview deploys
- Variables & environments — per-service env vars, production/preview/dev
- Node monitoring — host CPU, memory, disk, and network telemetry
- Security — audit logs, vulnerability scans, compliance reports
- Auth — Better Auth sessions (email + OAuth), per-user resource scoping
- Self-hosted networking — Traefik reverse proxy, optional Cloudflare Tunnel for exposure without port forwarding
Architecture
app/frontend/ React 19 + Vite + TypeScript + Tailwind + React Flow
app/backend/ Go API (Gin) · PostgreSQL · Redis · Docker SDK · Better Auth sidecar
infra/ Self-hosted compose: Traefik + Cloudflare Tunnel
docs/ Guides, OpenAPI spec, design documents
| Component | Default port |
|---|---|
| Frontend | 3000 (prod) / 5173 (dev) |
| API | 8082 |
| Auth sidecar | 3001 |
| PostgreSQL | 5432 |
| Redis | 6379 |
Quick Start
Docker Compose (everything)
cp .env.example .env # fill in secrets
docker compose up -d
Frontend at http://localhost:3000, API at http://localhost:8082.
Local development
docker compose up -d postgres redis # data services only
cd app/backend && go run ./cmd/server # API + embedded auth sidecar
cd app/frontend && npm install && npm run dev
Frontend dev server at http://localhost:5173.
Self-hosted with Traefik + Cloudflare Tunnel
See infra/docker-compose.yml and
docs/guides/CLOUDFLARE_SETUP.md.
Configuration
All configuration is via environment variables — see .env.example.
Required for production: JWT_SECRET, BETTER_AUTH_SECRET,
BETTER_AUTH_INTERNAL_TOKEN, database and Redis credentials.
Never commit .env or .env.prod. Both are gitignored; if a secret was
ever committed, rotate it.
Documentation
- docs/guides/ — setup, deployment, Cloudflare, autoscaling
- docs/api/openapi.yaml — API contract
- docs/developers/onboarding.md — contributor onboarding
- docs/design/ — UI design references
make help— common tasks
Contributing
See CONTRIBUTING.md. Issues and PRs welcome.
Security
See SECURITY.md. Report vulnerabilities privately — do not open public issues.
License
MIT © 2026 Tomas Dvorak