dear monkesses/monkmen,

I have always toyed with the idea of bundling one of those useful lightweight http daemon module you find in CPAN with my modules; so developers can easily develop and test code (as well as integrate webserver configuration) without worrying about setting up HTTP server. Then come 'production' deployment one could either manually or automatically generate appropriate apache conf.

I have had a few false starts, mostly to do with not having a lot of time to properly review http daemon modules, but more so in that most of the CPAN modules are too lightweight to represent regular Apache configurations.

Should I just use something like this and eschew with this kind of configuration management in perl... or has anyone had any successful approaches or identified a reasonably sane workflow from development to production ?

update I am seeking http daemon drop in that most reflects the mod_perl environment with Apache(1 or 2). Workflow would consist of several disparate developers using source control, developing and testing locally, then committing .. on post commit hook updates integration server with apache configuration. I know its probably not possible, but I am interested in smoothing out the workflow with respect to capturing changes in webserver configuration ... this may just remain a committed httpd conf file ;)

In reply to which http daemon module should I bundle ? by cutlass2006

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.