It's relatively easy to build Apache/mod_perl from source in a portable manner but very hard to use an existing install. This should make supporting more platforms easier.
Unless you expect your users to dedicate an entire server box to your application, they may not want to install a second mod_perl server on a single box.
And they may have discarded the Apaches that came with their distribution a long time ago.
I run a fly-weight apache, an apache+mod_ssl, and two separate apache+mod_perl servers (one mission critical, one not) on a single box.
IMHO, having an interactive script generating the appropriate Apache config bits and bobs would go a long way to addressing the issues of getting an installation right.
In reply to Re: Installation System Design for a Large Apache/mod_perl Application
by cleverett
in thread Installation System Design for a Large Apache/mod_perl Application
by samtregar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |