Coolify

# MISSION: Scaffold "Coolify" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **Coolify**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Coolify
- **What It Does**: Coolify is a self-hostable, open-source platform-as-a-service for deploying applications, databases and one-click services to your own servers over SSH, built as a PHP/Laravel monolith with Livewire, Redis-queued jobs and a self-hosted realtime layer.
- **Domain & Category**: Self-Hosted Cloud PaaS
- **Production Scale**: Solo
- **Development Mode**: AI-AGENT
- **Architectural Rationale**: A Laravel + Livewire monolith that bundles its own buildpacks (Nixpacks, Railpack) and a self-hosted Soketi realtime server lets one application both serve the dashboard and build/deploy arbitrary user code on remote servers without depending on external SaaS.
- **Live Website Reference**: https://coolify.io
- **Source Repository**: https://github.com/coollabsio/coolify
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: PHP, Laravel, Livewire, Tailwind CSS, Vite, PostgreSQL, Redis, Docker, Soketi
- **Primary Language(s)**: PHP, Blade, Shell
- **License of the reference repo**: Apache-2.0
- **Frontend**: Livewire — Server-driven reactive components render most of the dashboard (app/Livewire directory).; Tailwind CSS — Utility-first styling, version 4 via @tailwindcss/postcss.; Vite — Bundles and serves frontend assets for the Laravel app via laravel-vite-plugin.; xterm.js — Renders the in-browser terminal used to attach to deployed containers and remote servers.
- **Backend & APIs**: PHP — Runtime for the Laravel application, pinned to 8.4.; Laravel — Core application framework (routing, ORM, queues, auth) for the dashboard, API and CLI.; Laravel Horizon — Dashboard and supervisor for the Redis-backed queue workers that run deployments and scheduled jobs.; Pest — Test framework for unit, feature and browser (Dusk) tests.
- **Data & persistence**: PostgreSQL — Primary datastore, run as its own container alongside the app container.; Redis — Backs cache, sessions, and Horizon-managed queues.; MinIO — MinIO client (mc) is baked into the helper and app images for S3-compatible backup storage, alongside league/flysystem-aws-s3-v3.
- **Infrastructure & deploy**: Docker — Multiple docker-compose files and purpose-built Dockerfiles drive Coolify itself and the servers it deploys to.; Soketi — Self-hosted Pusher-protocol-compatible WebSocket server providing realtime broadcasting and the terminal bridge.; Nixpacks — Buildpack bundled into the coolify-helper image so Coolify can build user applications that have no Dockerfile.; Railpack — Second, newer buildpack bundled alongside Nixpacks in the helper image (with a musl-patched mise binary) for building deployed applications.; Sentry — Error tracking for the Laravel application.; GitHub Actions — Release/build workflows (coolify-release, coolify-helper, coolify-realtime, coolify-sha-build, coolify-testing-host) and a claude.yml workflow.
- **Tooling, testing & ops**: Laravel MCP — Ships a Model Context Protocol server (app/Mcp, .mcp.json) so AI agents can call Coolify's resources as tools.; Laravel Boost — AI coding-agent toolkit added as a dev dependency to give coding agents Laravel-aware project context.; Claude Code — Runs as a GitHub Action (claude.yml) for automated PR assistance in CI.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/coollabsio/coolify @ 255ee92)
1. **The app is a Laravel + Livewire monolith, not a decoupled API/SPA pair**: composer.json requires laravel/framework and livewire/livewire, and app/Livewire holds the bulk of the interactive UI as server-rendered components; Vite and Tailwind (package.json, vite.config.js) only handle asset bundling and styling on top of that, not a separate frontend application.
2. **Coolify bundles two buildpacks so it can build arbitrary user apps without a Dockerfile**: docker/coolify-helper/Dockerfile pins both NIXPACKS_VERSION and RAILPACK_VERSION and installs a musl-patched mise binary at the exact path Railpack expects, because "Railpack hardcodes a glibc mise download that fails on Alpine" — letting Coolify auto-detect and build a wide range of deployed repositories.
3. **Realtime and the in-browser terminal run through self-hosted Soketi, not managed Pusher**: docker/coolify-realtime/Dockerfile is FROM quay.io/soketi/soketi and additionally runs a custom terminal-server.js (built on node-pty and ws) so the dashboard's xterm.js terminal (package.json) can attach to remote containers over the same broadcasting channel used for deployment logs.
4. **Background work is Redis-queued and supervised by Laravel Horizon**: config/horizon.php configures the queue supervisor and composer.json requires laravel/horizon; the redis service in docker-compose.yml is a dependency of the main coolify service, so deployments and scheduled tasks run as queued jobs rather than inline requests.
5. **Ships its own AI-agent surface: an MCP server, an AI dev-tool dep, and Claude Code in CI**: composer.json requires both laravel/mcp (backing app/Mcp and the root .mcp.json) and, as a dev dependency, laravel/boost; a dedicated routes/ai.php route file exists alongside the standard web/api routes, and .github/workflows/claude.yml runs Claude Code as part of CI.
6. **Postgres, Redis and Soketi are sibling containers on a shared network, not embedded**: docker-compose.yml defines coolify, postgres (postgres:15-alpine, container coolify-db), redis (redis:7-alpine, container coolify-redis) and soketi (container coolify-realtime) services on one coolify bridge network, with the app container depending on all three.
7. **Production images are staged multi-build Dockerfiles separating install, build and runtime**: docker/production/Dockerfile has a composer-install stage (serversideup/php base), a separate node:24-alpine stage that runs npm run build for frontend assets, a minio-client stage, and a final serversideup/php runtime stage that copies vendor/ and public/build/ from the earlier stages and runs under s6-overlay with nginx.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Utilize Vite 6 with TanStack Router for fully type-safe routing. Manage server state and caching via TanStack Query v5 with optimistic UI updates.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (PostgreSQL, Redis, MinIO): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.