Forum Moderators: phranque
I have a set of sites (about 100) on a single domain such as :
www.example.com/ABC/...
www.example.com/DEF/...
Each has the same set of files beneath it, and I use apache security to manage who has access to which of those ABC/DEF domains. I'm using jRun for the heavy lifting, but am running into a deployment dilemma - there are individual files such as:
www.example.com/ABC/foo.shtml
..that are currently symlinks on my file server to a common directory. All of those sites (ABC, DEF, etc) symlink to the same location. There are about 90 of said sites and each gets many thousands of hits per day.
This presents a somewhat annoying deployment challenge. If I update one of those common files, everyone gets the new version. That might seem attractive in some csaes, but overall it isn't. What I need to do is to be able to specify which version of file foo.shtml each individual site uses. I'm limited to using Apache modules only; no CMS is usable here.
I came up with three quick-ish solutions:
1. Use mod_rewrite rules called from httpd.conf
2. Use mod_rewrite rules called from .htaccess files (means I don't need to restart httpd, but it's theoretically as fast as #1)
3. Use mod_alias statements in httpd.conf for each file
Each of these options means some overhead, but the overhead is far less than what I'm currently dealing with - I'd need only to change some aspect of the rule/statement to migrate one of these sites to a new version of a document such as foo.shtml.
So, to my question... are there any serious speed differences between these options, and if anyone has done any benchmarking I'd really enjoy seeing it.
Apologies for the long post... Thanks!
However, it may turn out that some of the options that make the mod_rewrite parser more complex may be useful to you.
Since you've got multiple domains, why not set up an A/B test?
So there's my highly-technical, non-committal opinion... :)
Jim
