Re: [Arsperl-users] Best Practices Question

[LJ L. <lj....@gm...>]

The way we have handled that here at my company is that each perl script
passes the $SERVER$ as one of the parameters.  We have an ini that's read
from each script that uses $SERVER$ as the ini file name which gives us
login, servername, etc

  _____  

From: Steve McDonald [mailto:Ste...@ch...] 
Sent: Wednesday, June 24, 2009 9:37 AM
To: ars...@ar...
Subject: [Arsperl-users] Best Practices Question


Good day all!
 
Like most programmers, I like to write code that is as portable across my
dev/qa/production environments as possible.  I've played with passing
arguments in workflow as well as reading control records located on each
server and each have their pluses and minuses.  How have you all handled
this in your environments when supplying the
servername/username/password/misc for the code you write?  Is there a better
way I've overlooked?
 
Solaris 10
Informix 10
ARSystem 7.1
 
As always, I appreciate your expertise.
 
 
Steve McDonald
Sr. Remedy Applications Programmer
Choice Hotels International