Comments on: 42foo: all the virtual hosts you need for your web development

By: Ryan Schumacher (@jrschumacher)

Ryan Schumacher (@jrschumacher) — Mon, 13 Feb 2012 16:41:08 +0000

So currently 42foo.com and Apache virutalhosts we can point to many different hosts using subdomains, but since I work on many projects on the fly I didn’t want to have to create all the virtual hosts. So I created that script so we could dynamically use sub domains based on directories.

Examples:

this:
/home/user/projects/project-category/project
becomes:
http://project.project-category.42foo.com

this:
/home/user/projects/project-category/project/branch
becomes:
http://branch.project.project-category.42foo.com

By: Jorge Bernal

Jorge Bernal — Wed, 11 Jan 2012 11:54:43 +0000

Not sure if I follow, but if it does what I think it does, you can use VirtualDocumentRoot for that http://httpd.apache.org/docs/2.0/vhosts/mass.html

By: Ryan Schumacher (@jrschumacher)

Ryan Schumacher (@jrschumacher) — Wed, 11 Jan 2012 09:27:17 +0000

Thanks, using 42foo.com in conjunction with this script to create wildcard subdomains:

https://gist.github.com/1593837

By: Marcelo Silveira

Marcelo Silveira — Mon, 05 Jul 2010 13:41:14 +0000

Very useful, thanks!

By: Local development – multiple vhosts - NiGhTHawK

Local development – multiple vhosts - NiGhTHawK — Wed, 22 Jul 2009 20:54:35 +0000

[...] hosts setup. It is rather annoying to keep updating the /etc/hosts file. I came across “42foo: all the virtual hosts you need for your web development” which has helped alot. But this was not enough, the virtual hosts are still static, then I [...]

By: Florian

Florian — Mon, 20 Jul 2009 09:37:45 +0000

The problem herein lies that I, and also most people I’ve talked to about this, don’t use 127.0.0.1, but their LAN IP – so that you can have other machines and colleagues access that as well.

Which doesn’t really make it easier, or even possible if you have dhcp with a low lease time, but still I found myself editing the hosts file too often to even start with the 127.0.0.1 approach

By: Kevin

Kevin — Fri, 17 Jul 2009 00:59:47 +0000

I recently wrote a similar tutorial which includes a shell script to set up the /etc/hosts entry and virtual host. If you removed the line that writes to /etc/hosts and used a *.42foo.com domain, it could automate the apache set-up for you.

http://blog.kevinmehall.net/2009/apache-local-vhosts

By: Rick Harding

Rick Harding — Fri, 17 Jul 2009 00:51:00 +0000

Thanks for the notes. I’ve tried to find different ways to handle this. I eventually found the /etc/hosts file easy enough to script adding/removing entries from. I have an addwebhost script that just appends the dns and copies a template vhost file into apache’s config.