meza deploy can be run to:
- Initially install everything
- Continue installing if an error occurs during install
- To apply changes after modifying configuration
- To apply changes after pulling a new version of Meza (e.g.
cd /opt/meza && sudo git fetch origin && sudo git reset --hard origin/master)
- 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.
- This happens ~2.5% of the time due to connections failing (e.g. Git failures) and ~2.5% of the time due to some Parsoid restart issue that has only been seen in Travis Continuous Integration builds, not locally. Ref Issue #604