Handelsregister App

Appearance

Coolify Deployment ​

Deployment Architecture ​

Coolify Configuration ​

  • One project: Connected to single Git repository
  • Multiple services: Different build contexts from same repo
    • Frontend: apps/web/ → Web service on port 3000
    • Workers: apps/workers/ → Background service, no port
    • Migrations: apps/supabase/ → One-shot service, runs before others
  • Shared environment: Variables available to all services
  • Independent scaling: Scale workers vs frontend separately

Service Dependencies ​

  • Migration service runs first - applies database changes
  • Application services start after migrations complete
  • Coordinated releases - single Git push updates everything

Environment Management ​

Shared Variables ​

  • Database connection strings
  • API keys and secrets
  • Feature flags and configuration
  • External service credentials

Service-Specific Configuration ​

  • Frontend: Port 3000, public-facing
  • Workers: Background processing, no public port
  • Migrations: One-time execution, dependency for other services

Deployment Benefits ​

Single Git Workflow ​

  • One push updates everything - no coordination between services
  • Atomic deployments - all services use same version
  • Simplified CI/CD - single pipeline handles multi-language deployment

Operational Advantages ​

  • Rollback safety - all services revert together
  • Environment consistency - shared configuration prevents mismatches
  • Scaling flexibility - independent scaling per service type