Deploying

Docker Compose

Bring a docker-compose.yml and Orizon runs your services together, routing public traffic to the one web service you choose.

How it works

When Orizon detects a docker-compose.yml, it builds and runs your stack in Compose mode. One service is the web service — the container that receives public HTTPS traffic — and the rest are internal dependencies your app talks to over the Compose network.

Choosing the web service

In the project's deploy settings you can set the web service name and the portOrizon should route to. Orizon overrides that service's published port so it can route traffic to it; the other services keep their Compose configuration.

shell

services:
  web:        # <- set this as the web service
    build: .
    ports:
      - "3000:3000"
  worker:
    build: ./worker
  cache:
    image: redis:7

One public entrypointCompose deploys expose a single web service publicly. For data you want to connect to from outside the app, consider a managed database instead of bundling one in Compose.

Environment variables

Project environment variables are injected into the web service. Reference internal services by their Compose service name on the shared network.

Dockerfile

Single-container builds with full control.

Managed databases

Provision Postgres, MySQL, Mongo, Redis and more.