I want to start by saying I really appreciate the excellent work hashicorp are doing.
It would be great if you could consider hosting a Debian package repo for Consul, this makes it much easier to manage updates and automated deployment.
Personally I find reprepo a very quick-and-easy tool for managing repositories - quick howto here: http://anonscm.debian.org/gitweb/?p=mirrorer/reprepro.git;a=blob_plain;hb=HEAD;f=docs/short-howto
There is also this service; https://packagecloud.io/ might come in handy.
While I don't agree that it's at all difficult to host an apt repo, that certainly does look like a good project.
I wouldn't say its difficult, it is just _another thing_ to maintain. Death by thousand paper cuts comes quickly with these things.
@sammcj Not difficult, but might be a nuisance. Essentially what @mitchellh said.
@sammcj Yeah I agree with @mitchellh. It's just yet another thing for us to maintain.
For anyone interested, I just started maintaining a Launchpad PPA for Ubuntu at https://launchpad.net/~bcandrea/+archive/ubuntu/consul. It currently targets LTS releases (12.04/14.04) which are the ones I need, but I might consider adding intermediate releases as well.
I use a (more or less) simple Makefile to produce the package - you can find it at https://github.com/bcandrea/consul-deb if you are curious.
thanks, @bcandrea!
The influxdb project makes good use of fpm for simultaneously building rpms, debs, and tars at the same time. https://github.com/influxdb/influxdb/blob/master/package.sh
It removes all details of maintaining the differences.
consul is a single binary, for easy (re-)distribution and handling.
Packaging as .deb is just a three-liner with fpm:
wget -N https://releases.hashicorp.com/consul/0.6.0/consul_0.6.0_linux_amd64.zip
unzip -o consul_0.6.0_linux_amd64.zip
fpm --force --verbose -s dir -t deb -n consul -v 0.6 --url=http://consul.io --vendor=HashiCorp --description "A distributed service discovery tool" ./consul=/usr/local/bin/consul
If you have not installed fpm yet, run gem install fpm before.
@geekq This assumes you have your own build infrastructure, can trigger it on updates to some public URI address and don't want to parametise anything like the version. Or are you really suggesting someone would type those commands out every time one wants to upgrade consul?
Most helpful comment
For anyone interested, I just started maintaining a Launchpad PPA for Ubuntu at https://launchpad.net/~bcandrea/+archive/ubuntu/consul. It currently targets LTS releases (12.04/14.04) which are the ones I need, but I might consider adding intermediate releases as well.
I use a (more or less) simple Makefile to produce the package - you can find it at https://github.com/bcandrea/consul-deb if you are curious.