Skip to main content
This page covers running the iii engine and its workers in a production environment. For local development, see the Quickstart and the Engine page.

iii Cloud deployments

The iii cloud subcommand group will manage hosted iii deployments. See CLI for the command surface as it stabilizes.
iii’s cloud will be available soon.

Deploy with Docker

Generate the Docker assets with the CLI and bring them up with Compose. Use iii project init --docker for a fresh project, or iii project generate-docker to add Docker assets to an existing one:
Both forms emit three files at the project root: Dockerfile, docker-compose.yml, and .env. Re-running the generator does not overwrite existing files, so edits you make to the templates stick. Start the stack:
The generated docker-compose.yml exposes: The Dockerfile builds against iiidev/iii:latest (distroless, non-root). The compose file ships commented-out Redis and RabbitMQ services that can be uncommented when workers need external adapters.

Configure a reverse proxy

The engine does not terminate TLS. Place a reverse proxy in front of it to handle TLS and route the three transport surfaces (/api/*, /stream/*, /ws) to the right ports.

Caddy

This is only an example configuration. Refer to the Caddy documentation for full configuration.

Nginx

This is only an example configuration. See the Nginx documentation for the full configuration such as SSL, header, and proxy options.