More installation methods

[arschles]

continues #40

• build RPMs and put into a yum repo
• apt-get
• homebrew
• others?

Any installation methods that we add should automatically build and publish to the appropriate repo on all updates to master

[kevmoo]

+1 on homebrew.

See a request for a password is SCARY. Most homebrew install avoid this.

[John-Lin]

homebrew +1

[gchatter]

Also note: services such as codeship don't let you run any commands via sudo: https://codeship.com/documentation/faq/root-level-access/. The work around is to curl to grab the linux command, then run it..seems like it'd be much easier though to do an npm install or gem install.

[rdallman]

I spent some time putting together a homebrew installation and have it basically working and passing all of their checks. I think the biggest thing stopping us from supporting a lot of alternative installation methods is going to be whether we can / can we invest the time to automate each release update. For homebrew it appears that this is going to be us forking (and keeping it open & up to date) homebrew, updating our formula file and sending in a pull request to their repo every time we do a release. Going to leave that exercise for another day (or another person).

initial support: https://github.com/Homebrew/homebrew-core/pull/27

$ brew install ironcli