I think setting it in apache is the easiest route You could refactor all your apps' environment (or other global) variables into one module and then source that at the beginning of each script. There are advantages and disadvantages to both approaches. Can you further explain why you prefer setting it via perl instead of apache?

Here's my stab at trying to figure out the best approach.

	Advantage	Disadvantage
Via Perl	no need for apache admin access, ability to change on the fly, no need to stop/start apache on changes	annoying code to keep track of meta data - especially if it never changes
Via Apache	Set it once and forget it, nothing special to do in code, meta data stays separated from code	Need to stop/start apache when it changes, gives devs a "how the heck does that work" headache if unaware of apache conf settings

-derby

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.