maestro_thoughts.md

1. read CMD instruction from dockerfile rather than require user to write it again in maestro.yml

• admittedly, having all the commands in one spot is easier to read
• from readme -- "Note: Command is required by the Docker Python api and having to specify it here can cause problems with images that pre-define entrypoints and commands."

2. support singular 'port' as well as plural in config section (like in require section)
3. fix 'mount' (should actually mount a host directory)

• ahh, maybe this will work: http://stackoverflow.com/questions/18208297/docker-remote-api-binds#18210059
  • does docker-py handle these options and, if so, can maestro pass them along?
    • looks like docker-py does, but I think maestro's not passing things along correctly
      • the readme's example should say 'binds' not 'bindings'
        • actually, maestro maps 'mounts' to 'binds'
    • this maestro code needs some TLC
      • why isn't 'volumes' just a list in the yaml?
        • why not only do the dictionary stuff in the code
        • why not use #values instead of items?
    • discovered my problem: I said "mount" instead of "mounts"
      • now I know a lot more about maestro than I did when I first came in

4. fix 'command' (should support &&)

• for now, how about '/bin/bash -c "your commands here"'