I like this pattern of using a distributed configuration store like etcd for load balancers so you can have a single configuration for a set of frontends. It is also great to have HTTP servers focused on runtime reconfiguration via APIs. A similar project that I have found useful is called Vulcan: http://vulcand.io/
In fact, I'm using https://github.com/mailgun/oxy, the reverse proxy Engine made by Mailgun to build Vulcand :)
Vulcand is awsome. But I wanted to build something simpler, that would work not only with etcd, but also with Docker, Mesos, Consul, etc.
For a norwegian (ØÆÅ, there you go, proof enough?), seeing someone
misspelling traffic as "træfik" immediately makes me think about some
guy from out in the country, with a semi-thick norwegian dialect and
bad, bad norw-english pronounciation.
"Træfik".
Americanized, with full prejudice, my best træfik character-impression
would be "Hey y'all. Howdy doodely do! What'cha got going on here in
the barn? Because that ain't no country or western I know!"
As a native American English speaker, when I see that, I really want to pronounce it as "tree-fik", in a similar way as we would pronounce caesar... maybe even make it really weird and say "tray-ee-fik" and that just isn't pleasant to say. :)
24 comments
[ 3.4 ms ] story [ 65.1 ms ] thread* How is the API authenticated?
* Does the API backend persist the configuration?
* Are there any plans for content-modification?
TIA!
"Træfik".
Americanized, with full prejudice, my best træfik character-impression would be "Hey y'all. Howdy doodely do! What'cha got going on here in the barn? Because that ain't no country or western I know!"
You get the picture :)
Besides, Træfɪk is not in the race of pure performance. It is fast and will be fast, but it's not my top priority.
> http://imgur.com/7iNx4btl.png
is the releases page
> http://imgur.com/LTJ5AfWl.png
is what I see when I unpack either the Zip or the Tarball.
I don't see a binary anywhere on there. I'd really like to try it out, though!