Curtis Poe wrote: > On Dec 30, 2005, at 10:39 AM, Frank Wiles wrote: > >> I'm not sure if it's what you're after, but have you thought about >> using an Include in your httpd.conf? > > > I'll look into see what's involved with that. In the meantime, what I'm > basically trying to do is allow a user to download our app and: > > perl Build.PL --server mod_perl2 > ./Build > # answer a few questions > ./Build test > sudo bin/httpd start
Admirable goal, but may I suggest an alternative way to look at it. Instead of working with an existing apache (which may or may not have mod_perl, mod_* or may have config directives which will conflict with your assumptions etc) why not have the app come bundled with it's own apache? > That's highly abbreviated, but I think that shows roughly the goal. Of > course, the above doesn't show the installation, but hopefully they > could run "sudo bin/httpd start" and it would restart Apache2 but with > the extra conf info available, such as where to find the mod_perl app, > extra libraries, etc. > > As much as possible, I'm trying to keep all of the app info in one spot > to make for easy installation/removal of the app without touching > anything else. The more configuration I force on the end users, the > less likely it is that they'll use the system. However, I'm pretty > damned clueless about the admin side of things and not sure how easy > this goal is to attain. This would also be accomplished by having your application contain it's own httpd. I would look at the build/install/control system of Krang (http://krang.sf.net). It will install a local version of Apache/mod_perl/mod_ssl and any needed Perl modules so that the admin/user doesn't have to think about any of that. A user could build their own app from source or download a binary built for their platform. -- Michael Peters Developer Plus Three, LP
