Meza/Deploy

can be run to:


 * 1) Initially install everything
 * 2) Continue installing if an error occurs during install
 * 3) To apply changes after modifying configuration
 * 4) To apply changes after pulling a new version of Meza (e.g.  )
 * 5) Maybe more scenarios

Perhaps another way to say it is that meza uses Ansible's way of thinking about things: instead of each step being in the form "install X" it is in the form "ensure X is installed'. The former cannot be performed more than once, but the latter can. This is called Idempotence.

See Meza/Commands for more detail on using Meza.