On Tuesday, July 2, 2002, at 10:58 AM, Analysis & Solutions wrote:
> Dude, that's nuts. It creates way more work. Having to put it on each > page in the first place, then having to change it before you put it up. > Then, there's the possibility that you forget to change it before > uploading. OUCH! <sheepish> In my case that could never happen. First, all the scripts for this site are based on a template, so I stamp out a new template which already has this line on it when I need a new script. But I also never use FTP/scp directly, I invoke scp from some shell/perl scripts I've written which "clean up" my files for me -- do things like rename the "dev" version to the "prod" version, move it to the appropriate directory of the appropriate machine, adjust the permissions appropriately, and do things like strip away certain lines (such as the aforementioned error_reporting() line). So in my case, I *never* forget, since nothing gets moved to production without going through the shell script... </sheepish> > Set error_reporting to E_ALL in php.ini on the development machine and > to > 0 in php.ini or .htaccess on the live server. Set it once on each > machine > and you're good. You're right -- that's a far better way to do it. I do my dev work in a separate virtual host on the prod machine though, so that's why I do it the way I described. (This prod server is a firewalled "intranet", as they call it, so is not really public, so I feel okay about doing dev work on it. I'm also kind of an amateur.) Erik ---- Erik Price Web Developer Temp Media Lab, H.H. Brown [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
