Switching to a the same OS doesn't solve this particular
problem. Of course there are advantages if your development,
testing and production areas all use the same platform, but
that has little to do with configuration issues. Typical
configuration issues include (but are not limited to):
user names, passwords, database names, database servers,
file and directory names, hostnames, and port numbers.
One way of dealing with it is by using environment variables,
but that quickly becomes unwieldy. A typical way of dealing
with this is configuration files. Configuration files could
be stored at a fixed location (say /etc/opt/app/application-name/config); a location relative
the program, the working directory during startup, or the
home-directory of the user; given as a parameter of the
program; passed via an environment variable; or some combination of them.
Abigail
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.