Tool for Docker containers management. It was conceived as a more powerful and elastic replacement for docker-compose.
== This tool is under heavy development and its API should be treat as unstable. ==
It was also not designed to manage docker containers on clusters of docker hosts.
I needed a tool similar to docker-compose, but with abilities to:
- define and reuse of container templates,
- define tasks to run on container stacks,
- define parameters to use by containers builders and group those parameters into stages,
- define deploys
- keep history of deployed configurations.
I also wanted to use a DSL instead of YAML file for configuration.
If you want to report a bug, please create a GitHub issue.
If you need help, please create a issue or contact me (but I prefer issues). You can find my e-mail on my website or tweet me.
If You want to contribute to the project, please feel free to fork it, create your feature/bug/hotfix branch and create a new pull request. I am using "git-flow"-like workflow to work with this repository:
-
There are two long-living branches: development and master. Master is always a "production" version. Development should always be in the "production ready" state.
-
There will be no release branches.
-
All production versions are tagged and merged from master into development.
If you want to add new feature, please create "feature/..." branch from development. If you want to fix a non-critical bug, please create "bug/..." branch from development. If you want to fix a "must-be-fixed-immediatly" bug, please create "hotfix/..." branch from master.
LOTC is versioned using Semantic Versioning specification. Please follow the specification when contributing - especially when creating a hotfixes (which always should be an a.b.X changes - so the backward compatibility must be preserved).
If you want to help but you don't know what to do - look at issues list.
This is free sofware licensed under MIT license. See LICENSE file.