Russ, I agree with you 100% but in Jenny's defense perhaps she meant "this" code rather than code in general. I have a few sites that are so simple I could see them in that light I suppose. Still as best practice I totally agree with you. In fact, such code is what keeps our business growing (ha).
-Mark Mark A. Kruger, MCSE, CFG (402) 408-3733 ext 105 www.cfwebtools.com www.coldfusionmuse.com www.necfug.com -----Original Message----- From: Russ Michaels [mailto:r...@michaels.me.uk] Sent: Saturday, April 23, 2011 6:43 PM To: cf-talk Subject: Re: IIS Question Jenny i'm not sure what evidence you have to quality that statement, but you couldn't be more wrong, bad code sure can take down a web server and even a database server, it happens every day. With 10+ years in the hosting business I personally see it happen all the time and consult with many customers to diagnose and fix the cause of the problem. On Sun, Apr 24, 2011 at 12:31 AM, Jenny Gavin-Wear < jenn...@fasttrackonline.co.uk> wrote: > > Hi Russ, > > See your point, but the actual likely hood of taking down a server with > code > is pretty small. > > You can always set up IIS/CF on your local PC anyway and avoid the problem. > The only issue then is the database, as you are unlikely to be running a > server o/s on your pc, assuming the database requires a server o/s - I'm > using MS SQL, for example. > > But yes, separate everything out. 2 web sites in IIS, 2 databases, 2 CF DB > connections, etc with very clear and regulated naming conventions. > > Jenny Gavin-Wear > Fast Track Online > http://www.fasttrackonline.co.uk/ > > > -----Original Message----- > From: Russ Michaels [mailto:r...@michaels.me.uk] > Sent: 23 April 2011 20:58 > To: cf-talk > Subject: Re: IIS Question > > > > as you are running both development and production on the same server I > would also suggest you take measures to isolate them as this is a very bad > setup you have as your untested development code could take down CF and > thus > the live site. > > I suggest you run CF multi in server mode and run 2 instances, 1 for live > and one for dev. > You should run every site on its own application pool to avoid any iis > issues. > > If you have no idea what any of that means, then you really shouldn't be > trying to manage a production web server for your client, so you should > speak with your host about management services or at least a hosting > control > panel that will do it for you. For windows I recommend Website Panel. > > On Sat, Apr 23, 2011 at 8:06 PM, Dave Watts <dwa...@figleaf.com> wrote: > > > > > > But confused if IIS can point to two different drives? How to find out > > which drive the IIS point out to.. I hope I am not vague with my question > > > > A single IIS server can have many IIS sites, or virtual servers. These > > can point to wherever you want them to point. Presumably, this machine > > has at least two IIS sites. You can view the list of sites in the IIS > > management console, and can right-click on each as Brian mentioned to > > see the filesystem location where each points. > > > > Dave Watts, CTO, Fig Leaf Software > > http://www.figleaf.com/ > > http://training.figleaf.com/ > > > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on > > GSA Schedule, and provides the highest caliber vendor-authorized > > instruction at our training centers, online, or onsite. > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343923 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
