Re: recursion or bad db request locking up browser

On Wed, 09 Apr 2008 06:33:55 -0400, Jerry Stuckle <jstucklex@xxxxxxxxxxxxx>
wrote:

Sir Robin wrote:
On Thu, 03 Apr 2008 10:10:49 -0500, Jerry Stuckle <jstucklex@xxxxxxxxxxxxx>
wrote:

Yes, you always should have a local development system. Never develop
on a live site!

You can - but you should do it on a subfolder with, for example, .htaccess
file that denyes access from all but allows your IP.

My local development system is also my public http server but I keep my
development stuff available only for "mr. 127.0.0.1".

No. You should always have a separate development system.

I didn't mean to claim otherwise - yes, you should. But I for example don't
(yet) have one and I only meant to point that in such scenario you _can_ do
this - with various limitations, security concerns, need to pay more attention
to things (which has it good sides too). You can - unless the limitations of
doing it this way make it impossible - but if you have another way to do it
then you shouldn't - of course.

For instance, not all of the PHP parameters can be set in .htaccess.
That's a minor concern; more of a concern is if you don something which
takes down the server. No, it *shouldn't* happen - but bugs in your
code and PHP working together can do it.

But the biggest reason is so you can duplicate the entire directory
structure, database, etc. on your development system. There is nothing
like having a problem when you go live because you accidentally had a
relative path wrong - or an absolute path pointing to the wrong
directory. Even worse is corrupting other files because you screwed up
something like move_uploaded_files(), unlink(), etc. And worse yet is
messing up your live database.

Too many things *can* go wrong. No, they may never do so. But the
purpose of a test system is to prevent problems like this from affecting
the live system. Using a directory on a live system for testing doesn't
do that, and is only slightly better than testing on the live system itself.

You make very good points here.

--
***/--- Sir Robin (aka Jani Saksa) Bi-Sex and proud of it! ---\***
**/ email: robsku@xxxxxxxxxxxxxxxxxx, <*> Reg. Linux user #290577 \**
*| Me, Drugs, DooM, Photos, Writings... http://soul.fiveam.org/robsku |*
**\--- GSM/SMS: +358 44 927 3992 ---/**
"I like the trees, you know? I like the way that the trees are on mountains,
all the different... the way the trees are."
.

Relevant Pages

  • Re: recursion or bad db request locking up browser
    ... not all of the PHP parameters can be set in .htaccess. ... But the biggest reason is so you can duplicate the entire directory structure, database, etc. on your development system. ... There is nothing like having a problem when you go live because you accidentally had a relative path wrong - or an absolute path pointing to the wrong directory. ... And worse yet is messing up your live database. ...
    (comp.lang.php)
  • Re: recursion or bad db request locking up browser
    ... No.  You should always have a separate development system. ... relative path wrong - or an absolute path pointing to the wrong ... messing up your live database. ... the live system. ...
    (comp.lang.php)