Please stop this. I don't care which is "better". Nobody (based on an informal survey of 1) cares. I have a preference based 95% on ignorance, with which I am quite happy. I'm not going to spend the rest of my life learning every damn platform just so I can die knowing "Russ was right".
-----Original Message----- From: Russ [mailto:[EMAIL PROTECTED] Sent: Monday, April 02, 2007 2:33 PM To: CF-Talk Subject: RE: OT ISAPI Rewrite > Well you can easily just create a logs/[sitename]/logfile structure in IIS > and point each site to their corresponding log folder, we do it all the > time. I'm still not seeing how to do this. I guess I can theoretically point each website to an individual folder, but then it will still create something like W3SVCXXXXXXXXX\exyymmdd.log. You don't have any control over this part. You also don't have control on what time the log file rolls over. Sure most people prefer 12am, but what if your servers are in a different time zone and you want it to roll over 11pm or 1am? > Why is it an extra step to do that backup process? Of which can be > automated > anyhow. > It is an extra step, whether you automate it or not. With Apache, it's just plain text files, and you can back them up without worry. You can also create a folder with all the virtual site configurations and have them generated automatically by coldfusion. For example, you can have a folder named vsites and you can have files such as sitename.com.conf which just needs to contain something like this: <VirtualHost *:80> ServerName *.example.com DocumentRoot c:/websites/example.com/ </VirtualHost> You can specify other options such as per site logging, but nothing else needs to be specified. I have just create a virtual site which will host all the subdomains for example.com, including www.example.com and user1.example.com and site2.example.com, etc. Try doing same with IIS without dedicating an IP to the site. You can have a directive in the main configuration file to include all the config files in this directory. Include conf/vsites/*.conf Voila. Have cf generate the text file, and restart apache to refresh the config, and you have just create an easy way to automatically create virtual sites. I wonder how long it would take you to do the same thing with IIS? > We get very good support from Microsoft as and when we need thanks, we are > a > big customer of theirs :-) > > I am still yet to find a decent argument on why anyone should use Apache > over IIS from your chosen arguments. > > True there is URL rewriting but then again, maybe you shouldn't need to do > this if your website structures are friendly out of the box :-) > It doesn't matter how good your website structures are, you need URL rewriting for SEO. It's also just a nice feature to have, and the possibilities with it are endless. Also lets say that someone else logs onto the box, and makes some configuration changes and breaks something. Do you know what they changed? Do you know how to fix it? Do you feel confident enough to restore from backup? With apache, you can keep the configuration in subversion, and know EXACTLY what was changed since last commit. You can revert the changes, roll back to a previous version, and all the other goodies that come with SVN. Apache is a developer's web server. It turns the web server into something you can write code for. I, for one, want to see all the configuration details of a particular site right in front of me, without having to flip through 20 different tabs. Russ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274344 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
