Skip to main content
All configuration for the self-hosted images is passed as environment variables. This page covers both editions; variables that only apply to the Enterprise image (onecli/slim) are marked. The full environment variable reference covers the gateway and CLI more broadly.

Core

If you don’t set ONECLI_ORG_API_KEY, the generated key is printed to the container logs exactly once, marked “Save it now — shown only once.” Prefer setting it yourself so the credential is pinned and never appears in logs.

Networking

The container exposes two ports: 10254 (dashboard and REST API) and 10255 (the gateway proxy agents connect to). Treat 10254 as an admin interface and expose 10255 wherever agents run.

Authentication

The first visit asks you to create an account — email and password. That account owns the instance; after it exists, joining needs an invitation. Create it right away: until you do, whoever reaches the host first becomes the owner. You can change your password any time from Account → Preferences, which also signs out every other session.

Database

The compose files in the deploy guides bundle PostgreSQL. To use an external or managed database instead, drop the postgres service and point DATABASE_URL at your database:
Migrations run automatically when the container starts, so the database user needs DDL privileges on the target database.

App integrations

Self-hosted instances connect apps with your own OAuth credentials: create an OAuth app with each provider, then supply its client ID and secret in the dashboard or pre-configure it with environment variables. The app credentials reference lists the variables for every app. Register the callback URL as:
For example, https://onecli.internal.example.com/v1/apps/github/callback. Per-provider setup is covered in the integration guides.