autoupdate issues for MVP about launcher

[groob]

Publish binary to notary.

Say you have a launcher or osquery binary, perhaps generated with the package-builder mirror subcommand from #69

First, upload the tar.gz files with the binaries to their respective folders in gs://binaries-for-launcher

Next, publish the updates to the notary server:
You will need the notary CLI tool - https://github.com/docker/notary#building-notary
You will also need the current keys (for now, shared in 1password). Extract the contents of notary.zip into ~/.notary

Examples:

# adds the tar file in `/path/to/tar` at the remote path of `darwin/launcher-stable.tar.gz` to the GUN kolide/launcher
notary add kolide/launcher darwin/launcher-stable.tar.gz /path/to/tar -p

# or osquery
notary add kolide/osqueryd linux/osqueryd-stable.tar.gz local-mirror/binaries-for-launcher/kolide/osqueryd/linux/osqueryd-stable.tar.gz -p

The GUN for the binaries are
kolide/launcher and kolide/osqueryd respectively.

Once published, if the launcher is configured for autoupdate, it will try to pull & replace the latest stable version as soon as it becomes available.

Relevant launcher flags:

  -mirror_url string
    	The URL of the mirror server for autoupdates
  -notary_url string
    	The URL of the notary update server
  -autoupdate_interval duration
    	The interval when launcher checks for new updates. Only enabled if notary_url is set. (default 1h0m0s)

Autoupdate is enabled, if the notary server url is not "".
The correct value is https://notary.kolide.com/.

[murphybytes]

Thanks @groob