It handles the .dev DNS resolution, and also supports hosting domains that you map through /etc/hosts (ex: foo.company.com if you need to share cookies with a SSO server, but don't want all of company.com directed to your local machine)
It is much easier to configure than Apache vhosts for distributing traffic based on host name:
* symlink to Rack app for Ruby support. Name of symlink becomes hostname
* create a directory and symlink Public for static HTML. Directory name is hostname
* as sibling said, put port # in text file to proxy traffic to another process. File name is hostname
I use Anvil for Mac to do some of my Pow management.
I'm also using Apache to do SSL termination and proxy to Pow, as well as host some other stuff. But Pow is so easy to use for both static sites and proxying to another web server, I prefer it.
It handles the .dev DNS resolution, and also supports hosting domains that you map through /etc/hosts (ex: foo.company.com if you need to share cookies with a SSO server, but don't want all of company.com directed to your local machine)
It is much easier to configure than Apache vhosts for distributing traffic based on host name:
* symlink to Rack app for Ruby support. Name of symlink becomes hostname
* create a directory and symlink Public for static HTML. Directory name is hostname
* as sibling said, put port # in text file to proxy traffic to another process. File name is hostname
I use Anvil for Mac to do some of my Pow management.
I'm also using Apache to do SSL termination and proxy to Pow, as well as host some other stuff. But Pow is so easy to use for both static sites and proxying to another web server, I prefer it.