Now we use a fixed filename pattern. Detect the war file instead.

Users might want to deploy Aggregate using MySQL servers. We should support writing the correct conf files for MySQL too.

https://forum.opendatakit.org/t/odk-aggregate-setup-on-digitalocean-with-mysql/19521/2

After silencing output (see -vv flag), the diff isn't printed out.

An install op would simplify the cloudconfig script by relying on this tool to make the first installation.

It would also require some changes that would probably make this tool useful for users that deployed manually their Aggregate servers.

This is needed for deployments that use proxies or load balancers

Add a restore op that takes the latest backup (or makes the user choose one) and deploys it

A new operation that generates a cloudconfig op would be useful:

• We could provide a shell/powershell oneliner that dowloads and runs this operation
• This operation should be a guided wizard that spits out the cloud config and removes itself once finished
• We could load the contents to the clipboard from the console
  • Linux xclip -selection c cloud-condig-yml

The update operation should be run with sudo.
Prevent the execution of the operation if we're not root

getodk/aggregate#401 introduces a new conf setting to avoid checking hostnames. The installer should read a new value from the conf JSON file and configure the security.properties file accordingly