use of LPCONFIG env setting forcing use of wrappers

[Steve McInerney]

This has been highlighted as a pain point issue in a recent request to create a rewrite config via apache.
A wrapper has had to be created for the sole purpose of setting the LPCONFIG for the environment(s) needed.

The problem is further seen in the mix of Makefile's, init scripts, crontabs and the like that all require setting of this env variable. ie. There is no single place that the application itself goes and looks for this crucial configuration setting.

Clearly there is still a need to have an override - where we have multiple services on the same server all with different configurations - but it would enormously simplify the modifications necessary to troubleshoot and manage lp services if a default path/config file were added.

One suggestion from discussions in IS was for:
"A search path of "$LPCONFIG:~/.lpconfig:/etc/launchpad/config" would be 12 kinds of awesome"

[Francis J. Lacoste (flacoste)]

There is such a default and it's 'development'.

I don't understand the problem here.

[Stuart Bishop (stub)]

On Tue, Feb 17, 2009 at 1:35 AM, Francis J. Lacoste
<email address hidden> wrote:
> There is such a default and it's 'development'.
>
> I don't understand the problem here.

The problem is that the default of 'development' is only appropriate
on developer boxes. The default on other servers needs to be set in
the shell startup scripts for interactive use, in the crontab for
batch job use, and now via wrappers for processes spawned by processes
running as other users, such as apache.

If nothing else, it will make our production and staging environments
cleaner because the LPCONFIG environment variable will only ever need
to be specified to override the default for that server.

[Francis J. Lacoste (flacoste)]

Fixed in RF 7799.