I've done this (semi-automatically) for a module before. Module::Build provides a way to save config data (see here). Then you can access the configuration by use-ing Foo::Bar::ConfigData and calling Foo::Bar::ConfigData->config('foo');. During build, you can also write config there ($builder->config(foo => 'blah');) whenever you want. I'm sure other packaging systems have similar features.
But if you're going this way, do consider writing a regular, user-editable config file instead. It will make your life easier when deploying. More importantly, it will make the devops' life easier. Configuration done via .pm files tends to be hard to modify by regular users.
It would also allow your module to be able to run with different instances of the front end, by providing the paths to different config files, something that is harder to do with a .pm file.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
