[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

Re: [Arsperl-users] Best Practices Question

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

Re: [Arsperl-users] Best Practices Question

Steve, A way that we did it was to create an encrypted file which contained the connection info. It could be a single file, similar to an SSH's known_hosts file. For our application we had multiple files, one for each server/username combination. It was probably not the most efficient, but