Releases
Straight from GitHub
Read from the repository's releases API and summarised automatically: each entry keeps the pull-request titles GitHub generated, minus the dependency bumps and release chores. Nothing here is hand-written — for the full text, follow through to the release notes.
- v1.7.2
- Latest version
- last week
- Released
- 21
- Releases
- 5 days ago
- Last commit
- MIT
- License
Built from the koduj-dev/docker-commander releases API
All releases- ChangeAn unknown `DC_…` key in the config file (usually a typo) and a line that isn't
- ChangeRoutine Go, npm and GitHub Actions dependency updates (minor/patch, plus
- ChangeBehind a path prefix, the session cookie is scoped to that path, so other apps
- v1.7.1 · last week
- ChangeGo, npm and GitHub Actions dependency updates (minor and patch only).
13 downloadable assetsRelease notes - v1.7.0 · last week
- ChangeMany fixes from a full review: localhost 2FA exemption behind a proxy, fail-closed policy rules, recovery-import validation, one operation at a time per project, and more.
- ChangeThe user manual in [`docs/`](https://github.com/koduj-dev/docker-commander/tree/main/docs) was rewritten with common tasks for every page.
13 downloadable assetsRelease notes - v1.6.6 · 2 weeks ago
- Change[docs] changelog 1.6.6
- v1.6.5 · last month
- Change[docs] stamp CHANGELOG for v1.6.5
Prefer the long form? The changelog follows Keep a Changelog, and the roadmap records what is shipped versus merely intended.
Roadmap
What is being considered next
Ideas, not promises — none of these has a date. The project's notes are deliberate about separating what shipped from what is merely intended.
Deploy verification
The one step the preview → policy → deploy → history → rollback loop still lacks: watch a project’s containers after a deploy, mark the revision verified or failed, and offer a rollback to the last verified one.
Incident timeline
Join alerts, Docker events, deploys, log matches and metrics into one explainable incident — what changed, what broke, and the revision to roll back to.
External checks
Outside-in HTTP(S) and TCP checks with certificate-expiry warnings, as a new source for the existing alert rules rather than a separate monitoring tool.
GitOps and webhook redeploy
Deploy a stack from a git repository and redeploy when the ref moves — or, smaller, an authenticated per-project URL that CI can call to re-pull and redeploy.
OIDC / SSO
Google, Azure and Okta login. LDAP — including group → role mapping — was step one.
Cross-host view and host groups
One screen across every reachable host, and hosts grouped by environment or team so alert rules and roles can be scoped to a group.