applications, not development. I get into this argument with my provider all
the time.... especially when the servers become unresponsive due to someone
developing on them.
In an ideal world you would have any errors generated in your production
environment logged or emailed so that you could remedy the problem in a
development and/or test environment then move the changes to production once
you were confiedent they worked. This is all SOP usually, but hosting
companies have a hard time enforcing the "no development" rule in a shared
environment.
Oh well...
Mike
_____
From: Jeffry Houser [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 01, 2004 10:36 AM
To: CF-Talk
Subject: CF Administration Best Practices on Production Servers
Hi All,
I just want to check myself here to make sure I'm based in reality.
It would be considered a best practice to turn off debugging on
production servers, correct? My host has it turned on to help developers
test their code. They insist I must turn it off using cfsetting. I've
been arguing, unsuccessfully, that they should not allow people to
test/develop their sites on "production" servers.
So, am I completely off-base or is this considered bad?
--
Jeffry Houser, Web Developer <mailto:[EMAIL PROTECTED]>
Aaron Skye, Guitarist / Songwriter <mailto:[EMAIL PROTECTED]>
--
AIM: Reboog711 | Phone: 1-203-379-0773
--
My Books: <http://www.instantcoldfusion.com>
Recording Music: <http://www.fcfstudios.com>
Original Energetic Acoustic Rock: <http://www.farcryfly.com>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
