Containly 2.7.3: compose override files, API tokens for CI, Prometheus export

Containly 2.7.3 is out. It fixes how stacks with override files are handled and opens Containly to your CI pipelines and to Prometheus.

Compose override files (fix)

Containly now passes every compose file of a stack to Docker: the files Docker recorded for the project, or the main file plus compose.override.yaml like docker compose does. Until now an explicit -f made Docker skip the override file, so services defined only there (for example Mailpit) were ignored by deploys and version updates.
Version updates find the tag in override files and .env and change exactly that file; on a failed deploy every changed file is restored.
The stack editor shows override files as tabs next to the main file, and the check before deploy includes their changes.

API tokens (Free)

Profile > API tokens: personal tokens with the permissions Read, Redeploy stacks (optionally only picked stacks) and Prometheus metrics, optional expiry, shown once, stored only as a hash, revocable. Admins see every token under Settings > Integrations.
A token never does more than its owner's role and shows in the audit log as "user (Token: name)".

CI redeploy (Free)

One curl from GitHub Actions, Gitea or Forgejo Actions redeploys a stack: git pull for Git stacks, image pull and docker compose up -d with all compose files. The answer is a job you poll until it says ok.

Prometheus export (Free)

Settings > Integrations switches on /metrics (off by default): hosts up, CPU, memory and disk, and per container state, health, restarts, CPU and memory, with a ready scrape config; Grafana queries are in the guide. Served from Containly's own samples, protected by a metrics token, inbound only.

Update
docker compose pull && docker compose up -d (or the self-update under Settings > Version and licence).

Guides:

Reply