Re: Best approach to store Application Configuration
Fred Moyer <[email protected]>
| Newsgroups | gmane.comp.apache.mod-perl |
|---|---|
| Message-ID | <CAHrynWDCRDE2RH0SEtN+C+_8HVsJsZJJBo3s_3wHPY+u6AHqZw@mail.gmail.com> |
On Mon, Jul 11, 2011 at 2:23 PM, Michael Peters <[email protected]> wrote: > On 07/11/2011 05:16 PM, James B. Muir wrote: >> >> This page describes pretty well how to set up custom configuration >> directives; perhaps helpful? >> >> http://perl.apache.org/docs/2.0/user/config/custom.html > > I would almost always avoid this kind of configuration and go with an > external configuration file. Every project of any decent size will have some > scripts or processes that don't run under mod_perl and thus can't use this > apache-only configuration. This kind of configuration has the advantage of avoiding the overhead associated with PerlSetVar if I recall correctly. The downside is that the custom config directives can be a bit tricky to setup correctly. > As for configuration in Perl if I were starting a new project, I'd probably > go with something like Config::Any and then pick a backend format. +1