[CentOS] apache env vars - best practices

Les Mikesell lesmikesell at gmail.com
Mon Oct 19 19:11:10 UTC 2009


aurfalien at gmail.com wrote:
> I've been setting custom env vars for Apache 1 of 2 ways;
> 
> 1 - Changing the passwd file so Apache has a shell and loading a  
> custom .bashrc file.
> 
> 2 - Using the SetEnv directive in my httpd.conf file.
> 
> I'm crazy about neither one as they both have limitations;
> 
> 1 - I don't like giving Apache its own shell.
> 
> 2 - The SetEnv directive only takes 2 args so if I have a var with  
> multiple values like a path, it won't work.
> 
> What's the cleanest way to set complex env vars for Apache?

I'm not aware of any exceptions to environment variables being single 
key/value strings.  The value of a path is a single string as far as the 
environment mechanism goes, even if the code that evaluates it splits on 
:'s by convention.  I don't think there is such a thing as a complex env 
var.

-- 
   Les Mikesell
    lesmikesell at gmail.com


More information about the CentOS mailing list