Harbormaster
Do you have apps you want to deploy to a server, but Kubernetes is way too much? Harbormaster is for you.
Harbormaster is a small container orchestrator that lets you run multiple Docker Compose applications on a single host, with automatic deploys/restarts, simply by pushing to a git repo.
It does this by taking a list of git repository URLs that contain Docker Compose files and running the Compose apps they contain. It will also handle updating/restarting the apps when the repositories change.
Please visit the documentation for more details.
If you want an LLM to set up your Harbormaster app for you, point it at llms.txt. That file is a single-page guide with everything an agent needs to write your configuration and convert your Compose app.
Rationale
Do you have a home server you want to run a few apps on, but don't want everything to break every time you upgrade the OS? Do you want automatic updates but don't want to buy an extra 4 servers so you can run Kubernetes?
Do you have a work server that you want to run a few small services on, but don't want to have to manually manage it? Do you find that having every deployment action be in a git repo more tidy?
Harbormaster is for you.
At its core, Harbormaster takes a YAML config file with a list of git repository URLs containing Docker Compose files, clones/pulls them, and starts the services they describe.
You run Harbormaster on a timer, pointing it to a directory, and it updates all the repositories in its configuration, and restarts the Compose services if they have changed. That's it!
It also cleanly stores data for all apps in a single data/ directory, so you always
have one directory that holds all the state, which you can easily back up and restore.
See more details in the documentation.
1 maintainer
Release files for docker-harbormaster 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| docker_harbormaster-0.4.0.tar.gz | 31.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docker_harbormaster-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.9 kB
Release files / docker_harbormaster-0.4.0.tar.gz
| Download URL | docker_harbormaster-0.4.0.tar.gz |
|---|---|
| Size | 31.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02429665bb0dc07c45ac7ab6d59f41274b32711663a14ec5a64b9f7cff4606ee
|
|
BLAKE2b-256 checksum How to use checksums |
2ec465c170872270dc6ac58b5c66450ec6dd611626dce9edf9b213a22d7930f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / docker_harbormaster-0.4.0-py3-none-any.whl
| Download URL | docker_harbormaster-0.4.0-py3-none-any.whl |
|---|---|
| Size | 32.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c84d9b5dc6549187e8621d112f3ba378588f6a48bdfebddf9d1ebd78b2c5ba7e
|
|
BLAKE2b-256 checksum How to use checksums |
8f6985850c44cb2d4808f6f7c221cbfbaee1974bc95ec6c797b2f4bf576d5327
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log
