Version 0.4.1

v 0.4.1

• Added support for passing docker-compose commands when swarming in
  project files: -kill, -start, -rm, etc.
• Fixed output bug so we get (again!) a list of running components
  once compose operations have ended.

v 0.4 (never released)

• Added support for substitution of (local) environment variables as a
  workaround for this
  highly-requested missing
  feature of compose. However, this means that, when crafting compose project
  files to use the feature, you will not be able to use them directly outside of
  machinery, unless you run them through
  envsubst
• Adding support for "poor man's discovery". machinery automatically declares
  and caches environment variables with network information for the created
  machines. These variables can be, for example, used when starting components
  through compose (see above).
• Adding support for logging in at one or several registries at the docker
  daemon running within a specific virtual machine. Note that you will have to
  start the components under the same user than the one that was automatically
  logged in.
• Adapting to new versions of docker, docker-machine and docker-compose.
• Automatically trying to update a machine to the latest boot2docker.iso
  when the installed version of docker is lower than the one of the local
  installation.
• Arrange for the temporary files created for performing environment variable
  substitution to point back correctly to the source files when using extending
  services with compose.
• Adding an env command to export all machinery network details to shell.
• Extending the swarm command so it takes a list of compose project files, or
  indirections to compose project file in a format similar to the compose key
  of the YAML syntax. These projects will be sent to the swarm master for
  creation.
• Adding a reinit command to trigger some of the machine initialisation steps,
  such as image downloading or component creation.