Add vhost name based activation strategy #88
The activation strategy that will use the Virtual Host (vhost) server name
I left one TODO - support for wildcard in domain name (like *.beta.example.com).
Btw, I had problem with a name for this strategy. The current one sounded sensible
The activation strategy that will use the Virtual Host (vhost) server name used in the request to decide if the feature is active or not. This strategy can be useful when given service instance is available through two different Virtual Host names (vhosts like www.example.com and beta.example.com) each with different features enabled. By the way test dependencies update and unification.
Hey! Awesome! Thanks a lot for this contribution!
Sorry that it took so long for me to answer. I was traveling and really really busy. So sorry about that.
I merged your pull request. It looks good. However I renamed the strategy to
Thanks again! Great work! :)