which http daemon module should I bundle ?

cutlass2006 has asked for the wisdom of the Perl Monks concerning the following question:

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 ;)

Comment on which http daemon module should I bundle ?

Replies are listed 'Best First'.
Re: which http daemon module should I bundle ? by Corion (Patriarch) on Oct 20, 2008 at 06:51 UTC
I'm fond of HTTP::Server::Simple. But as you don't tell us what/how the workflow of your developers would be, it's hard to recommend something else. HTTP::Server::Simple is usually used to load another module with then runs the code handling the request. If you want an environment that looks even more like CGI, or even more like mod_perl, you'll have to use a full server that implements these to the extent you need them. As an aside, you don't need to distribute HTTP::Server::Simple with your modules. CPAN will happily download and install HTTP::Server::Simple if you list it as a prerequisite of your module in your `Makefile.PL` .	[reply] [d/l]

Replies are listed 'Best First'.

Re: which http daemon module should I bundle ?
by Corion (Patriarch) on Oct 20, 2008 at 06:51 UTC

I'm fond of HTTP::Server::Simple. But as you don't tell us what/how the workflow of your developers would be, it's hard to recommend something else. HTTP::Server::Simple is usually used to load another module with then runs the code handling the request. If you want an environment that looks even more like CGI, or even more like mod_perl, you'll have to use a full server that implements these to the extent you need them.

As an aside, you don't need to distribute HTTP::Server::Simple with your modules. CPAN will happily download and install HTTP::Server::Simple if you list it as a prerequisite of your module in your Makefile.PL

[reply]
[d/l]