A reverse proxy would send all traffic to a given path to another server internally (or externally). It's probably overkill if you can get the correct rewrite rules but I've come to wonder how I lived without them in my development world. All of your relative paths would then work based off the base url since they're actually getting served under that context.
domain.com/site/
domain.com/v2/
You can also do stuff like put one reverse proxy in front of all developer machines and use named virtual hosts to pass through to internal dev machines and not have to open lots of alternate ports on the firewall.
Again, overkill for your problem probably, but they're super cool. Not to mention pretty much required for high availability/load balancing.