machinery
machinery copied to clipboard
efrecon
Easily control entire docker-machine based clusters from the command-line.
Machinery automates (applications) stacks deployments through the `applications` key in the YAML file format. For the time being, only one YAML file can be deployed, while `docker stack deploy` supports...
When no YAML file is found in the current directory, we should produce an error early, instead of the following: ``` [NOTICE] Automatically picking YAML file at: couldn't open "":...
With new features like `include` and `extends` comes many possibilities, but also additional complexity. `machinery` should provide a command to dump back the readily extended YAML after all inclusions to...
The file format contains a version number. `machinery` should start to map new features that imply changes to the file format to new version of the file format. This should...
Fail early when one of the steps of the (re) initialisation fail, instead of continuing.
As it is now possible to "tweak" machines based on the content of environment variables, i.e. by setting these in the `environment` section for example, using the content of these...
When specifying machine names or aliases that do not exist, `machinery` should properly print out a warning.
The current implementation will request the underlying OS for its mounts a number of times, we should implement a cache to improve startup times.
When running from windows the full path that is passed to the local ssh implementation should contain forwards slashes (as in `C:/Users/emmanuel/shadowing/usb/myJoice/dev/backend/config/security/certs/ssh/id_rsa`) while the current implementation passes fully-qualified backslashes (as...
When using good old compose , rolling updates might be something we would like to consider. [This](https://stackoverflow.com/questions/49090395/how-to-achieve-a-rolling-update-with-docker-compose) has the basis for performing such updates. As this perhaps isn't the expected...