top | item 7769489

(no title)

bkirkbri | 11 years ago

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.

discuss

order

bketelsen|11 years ago

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|11 years ago

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...