Outpatient clinic/Dept. of self-hosting
Docktor deploys, monitors, backs up and updates the Docker Compose stacks on one server, from your browser. You don't need an SSH session.
Directory
Patient pathway
Start Docktor with one compose file and finish the setup wizard.
Scan the host for running Compose projects, or deploy a new stack.
Edit, update, back up and put a domain in front of each stack.
Second opinion
They're all good tools with different specialties. Docktor sees one host and treats the whole stack: files, backups, domains, health checks and updates.
| Capability | Docktor | Portainer CE | Dockhand | Dockge | Komodo |
|---|---|---|---|---|---|
| Several hosts | One host, by design | Agent per host | Socket, agent or TCP | Agents, since 1.4 | Periphery agent |
| Backups of stack data | restic, scheduled | Not in CE | restic, scheduled | ||
| Reverse proxy & Let's Encrypt | Built in | ||||
| Image update checks | Apply when you choose | Business edition | Tracked per image | Manual pull | Scheduled |
| Adopt running Compose projects | Adopt or migrate | Limited control | Read-only | Move into stacks dir | Set up per stack |
| HTTP health probes & uptime | With incident history | ||||
| No paid tier | MIT | zlib, paid Business | BSL 1.1, paid for business use | MIT | GPL-3.0 |
Prescription
Docktor runs as the app and a bundled Postgres database, from a published image for amd64 and arm64. You don't build anything or install a database. Your compose files stay on disk as the source of truth.
Patient one Linux host, Docker Engine, Compose v2
# fetch docker-compose.yml and .env, fill in CHANGE_ME
$ docker compose up -d
$ docker compose logs -f docktorSig. Once. Repeat docker compose pull to upgrade.
Refills unlimited · MIT licence