"Live" Apache Virtual Hosts

andrewdodd13 · 28 May 2009 at 23:58

I'm intending to set up a soft of Software-As-A-Service system, using Apache and a load of other things. Basically, each registered customer/user gets a URL such as
http://www.example.com/<customer name>/
I'm hoping to provide a service whereby a user can register their domain name, and have their DNS records point to us, and we will redirect traffic from their domain to their URL automatically.

I'm under the impression that I'll need to use Apache's VirtualHost functionality to achieve this, but any edits to the configuration files require a restart of Apache, and I'd like to avoid this scenario.

Are there any ways around this?

andrewdodd13 · 29 May 2009 at 10:55

That will work I guess, but it won't put them in the correct location automatically, will it?

I also considered doing that and using mod_rewrite for a while, but I came up with a problem... which I appear to have forgotten for now... hmm.

andrewdodd13 · 29 May 2009 at 11:09

Graceful looks fairly cool, I didn't know about that, thanks.

As for the re-writing, I think the problem actually was that we were going to leave theirdomain.com (so that you have theirdomain.com/index.php => ourdomain.com/them/index) but some of the application code uses hard-paths (ie. links to index.php point to ourdomain.com/them/index.php and not just index.php); I guess I'll just have to fix that.

Thanks for the help.

andrewdodd13 · 29 May 2009 at 18:13

daz said:
A graceful restart on a busy box with a lot of vhosts can give 10-30 seconds downtime.

If I read the manual right, this seems to be contrary to the documentation which states that there will always be the correct number of threads to serve clients, or am I missing something?