southclaws/machinehead

A docker-compose application manager that deploys and maintains a set of compose projects and provides secret management for them via Vault.

machinehead's Issues

Authentication for private git repositories

In order to support private git repos, Machinehead requires basic auth at the very least.

SSH would be a nice to have, not sure on the complexities of implementation yet.

Make all daemon errors non-fatal

Currently, if the daemon encounters an error with

• loading secrets
• running compose
• receiving an error from gitwatch
  It will exit.

In production, this is not desired behaviour so these errors should be logged but not cause an exit.

However, there should be some way of signalling an exit inside start in the rare case that it's not possible to continue operating after an error.

Expand `targets` to contain more options

targets should not just be a list of URLs (as simple and elegant as that was) but a list of objects where additional properties can be set.

• Per-project environment variables
• Auto-generate a .env file for each project for testing - so the user can run docker-compose commands manually while still using all the secrets that were loaded from vault (#7), the global .env and the per-project environment variables section above
• Disable automatic refreshing of this service

Hot-reload of configuration

Dependent on #2

Configuration should be reloaded at runtime (fsnotify) in order to facilitate zero-downtime reconfigurations.

Reloaded configuration should not cause a failure, if the new configuration results in an error, the original configuration should be used as a fallback.

Add command line interface

It would be useful to provide a CLI for options such as config location and version.

Move configuration to JSON, make .env pass through

Environment variables read from .env should pass through to all applications, as a way to set global variables.

Load configuration from a JSON, YAML, TOML file

Configor would be a good choice for this.

However, Configor brings its own logs, which I'm against. So I may fork it and either remove logs or provide an event stream for logging.

Fully implement and test Vault support for secrets

Currently, some Vault code is in but it doesn't really do anything and hasn't been fully tested.