Apache 2.0 Goes Beta
Great news from the Apache Conference. A new version of Apache 2.0 has been released as a beta. You can find more information in their announcement. In other news according to Roy Fieldling's talk on the state of Apache, as of their next fiscal year individuals should be able to make tax deductible contributions to the Apache Foundation.
I've inherited & since further adapted the installation that has been running at work, and I don't relish the idea of having to merge together the current httpd.conf file & various binaries into those of a newer version. If nothing else, all the various redirects, aliases, raven-ssl settings, etc that we're currently using would, I assume, be trampled by a stock upgrade. Further, I don't want to just maintain the current httpd.conf file on top of an upgraded installation, because it doesn't make any mention of some of the newer features that would become available and that I'd like to take advantage of.
Are there tools out there to merge in old settings with a new installation? I don't like the idea of mucking around with diff scripts to do this, but to date I haven't been able to think of any better alternatives. Can someone help?
DO NOT LEAVE IT IS NOT REAL
Prevent email address forgery. Publish SPF records for y