Device Testing Local Virtual Hosts

Jeremy Frank, UI Development Director

Article Categories: #Code, #Front-end Engineering

Posted on

The front-end developers here at Viget use local virtual host configurations in Apache for each client project we’re individually working on. It’s a great way to be able to switch gears from one project to another if needed. However, when it comes to testing any one of those client projects with another device on the local network, well, that’s where things can get tricky. Whether its port numbers, editing the order of vhosts, or some complicated device specific configuration, there are definitely some technical and workflow hoops to jump through. Here’s a setup I’ve recently started using that eliminates those hoops.

The Secret Ingredient

Assuming you’re already setup with virtual hosts in Apache and have Web Sharing enabled in System Preferences1, you’re most of the way there. The key ingredient is to use the ServerAlias directive with xip.io.

<VirtualHost *>
  ServerName "myproject.local"
  DocumentRoot "/Users/jeremy/Sites/myproject"
  ServerAlias myproject.local.*.xip.io
</VirtualHost>

The ServerAlias directive allows for alternate names that Apache should map to the virtual host. The xip.io domain is a free wildcard DNS service from 37signals, which essentially resolves to your local ip address, and sends it back in the response. Now just fire up your various mobile devices and browse to the server alias above, substituting * with your local ip address.

http://myproject.local.[local ip address].xip.io/
http://myproject.local.127.0.0.1.xip.io/

What makes this so streamlined is that it allows for a consistent naming pattern that is easy to remember, and it removes unnecessary complication. As a bonus, it really comes in handy when a request comes in from a project manager to troubleshoot an issue on a recent project that you still have running on your local machine.

So that’s my setup. How can it be improved? What device testing tricks are up your sleeve?


1 Apple chose to remove the web sharing option in Mountain Lion. To get this working again you can run a series of commands in terminal, or simply install this preference pane by Tyler Hall. I’m still on Lion currently so I’m not yet affected by this change.

Jeremy Frank

Jeremy is a UI Development Director who bridges the gap between design and engineering, with a focus on optimizing web performance and enhancing accessibility.

More articles by Jeremy

Related Articles