Orchestrator Deployment
Development
1# Start the orchestrator: gRPC on 127.0.0.1:50051, REST API on 127.0.0.1:80802DATABASE_URL=postgresql://orcher:orcher@localhost:5432/orcher ./target/release/orchestrator34# Or use the CLI5orcher server start --foregroundDocker Compose
A Compose file for the full stack. The orchestrator serves both gRPC (50051) and the REST API (8080), so it is the only Orcher service:
1services:2 postgres:3 image: postgres:154 environment:5 POSTGRES_DB: orcher6 POSTGRES_USER: orcher7 POSTGRES_PASSWORD: orcher8 ports:9 - "5432:5432"10 healthcheck:11 test: ["CMD-SHELL", "pg_isready -U orcher"]12 interval: 10s13 timeout: 5s14 retries: 51516 pgbouncer:17 image: bitnami/pgbouncer:latest18 depends_on:19 postgres:20 condition: service_healthy21 ports:22 - "6432:6432"2324 orchestrator:25 image: ghcr.io/orcher-io/orcher26 depends_on:27 postgres:28 condition: service_healthy29 environment:30 DATABASE_URL: postgresql://orcher:orcher@pgbouncer:6432/orcher31 LOG_LEVEL: info32 # The image listens on 0.0.0.0, which requires authentication.33 # For a local, unauthenticated stack only; configure [security] for production.34 ORCHER_INSECURE: "true"35 ports:36 - "127.0.0.1:50051:50051"37 - "127.0.0.1:8080:8080"38 healthcheck:39 test: ["CMD", "curl", "-f", "http://localhost:8080/health/live"]40 interval: 30s41 timeout: 3s42 start_period: 5s43 retries: 31docker compose up -d23# View logs4docker compose logs -f orchestrator56# Scale orchestrators for high availability7docker compose up -d --scale orchestrator=3Using systemd
Create /etc/systemd/system/orcher-orchestrator.service:
1[Unit]2Description=Orcher Orchestrator Server3After=network.target postgresql.service45[Service]6Type=simple7User=orcher8Group=orcher9EnvironmentFile=/etc/orcher/orchestrator.env10ExecStart=/usr/local/bin/orchestrator11Restart=always12RestartSec=513StandardOutput=journal14StandardError=journal15SyslogIdentifier=orcher-orchestrator1617NoNewPrivileges=true18PrivateTmp=true19ProtectSystem=strict20ProtectHome=true2122[Install]23WantedBy=multi-user.target1sudo systemctl daemon-reload2sudo systemctl enable orcher-orchestrator3sudo systemctl start orcher-orchestrator4sudo journalctl -u orcher-orchestrator -fNext Steps
- Orchestrator Overview — Architecture and components
- Configuration — Environment variables and database connection
- High Availability — Multi-instance deployment and load balancing
- Monitoring — Health checks, performance tuning, and troubleshooting