From: Bill Stephenson
>
> On Sep 12, 2012, at 9:18 AM, Mark Haney wrote:
> > My question is, what IS standard practice for this?
>
>
> I use a few different methods. One is to make the changes on the dev box,
> then use BBEdit to "Compare" that to the file used on the live server. BBEdit
> allow
On Sep 12, 2012, at 9:18 AM, Mark Haney wrote:
> My question is, what IS standard practice for this?
I use a few different methods. One is to make the changes on the dev box, then
use BBEdit to "Compare" that to the file used on the live server. BBEdit allows
me to copy just the lines of code
On Wed, 12 Sep 2012 10:18:49 -0400, Mark Haney wrote:
> I've got what I hope is an easy question to answer. I've got a perl web
> app that I've setup with a 'live' version (more like a beta actually)
> and a dev version for me to make changes to that might break the other
> site.
>
> The way I i
On 09/12/2012 10:57 AM, Rob Dixon wrote:
Hey Mark
I suggest you use set the MYLIBPATH environment variable to the
directory you want to use and then do
use lib $ENV{MYLIBPATH}
at the head of your program
HTH,
Rob
Thanks Rob, I'll look into it.
--
Mark Haney
Software Developer/Consu
On 12/09/2012 15:18, Mark Haney wrote:
I've got what I hope is an easy question to answer. I've got a perl web
app that I've setup with a 'live' version (more like a beta actually)
and a dev version for me to make changes to that might break the other
site.
The way I inherited it was as a singl
On Wed, 12 Sep 2012 10:18:49 -0400
Mark Haney wrote:
> My question is, what IS standard practice for this?
The standard practice is to ensure that the development, test, and
production environments are exactly the same. Even the smallest
difference can cause no end of problems.
--
Just my 0.0
