[bkirkbri]

What great timing! I was just about to roll my own using etcd, haproxy and a bunch of perl duct tape.

Very excited to take a good look at vulcand.

[robszumski]

If you're still interested in doing this for any reason, check out confd [0] for populating templates based on etcd values.

[0] https://github.com/kelseyhightower/confd

[bkirkbri]

Yes, confd was on my radar and looks promising. In my case, we've already got a wad of perl duct-tape out there and adding etcd was a baby step. Using confd would have been a later step.

Vulcand will likely allow me to replace the whole shebang in one step.

[bketelsen]

it doesn't look like vulcan supports HTTPS, so it's a no-go for anything serious. Here's a post on my confd/nginx/docker setup for zero-downtime using etcd. http://brianketelsen.com/2014/02/25/using-nginx-confd-and-do...

[bkirkbri]

I actually learned about confd via your post. Thanks for that.

In our case, HTTPS isn't an issue but there are good arguments for using a tried-and-true proxy. I see Vulcan as a quick way to test out docker containers for our architecture.

In the end I'll probably use confd to rewrite a VCL file for Varnish. It's just a matter of deciding how many containers and what level of sidekicking/ambassadoring I'm willing to put up with to "properly" organize things...

[alexk]

Yep, until this won't be closed:

https://github.com/mailgun/vulcan/issues/31

Vulcand should not be used as for anything frontend-related