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.

They don't have to, I'll do it for them! Basically, you install the app, call it x3000. You start x3000 thus: 

  /usr/local/x3000/bin/x3000_ctl start

[download]

Unless you peek under the covers you won't even know it's using Apache. All you need to know is that when you go to the address and port you configured for x3000 you get the x3000 web interface. This is true for Bricolage too, actually. In both cases the user doesn't interact with Apache unless they choose to.

But to answer your question directly, no the app doesn't need its own server, just two ports (one for HTTP and one for FTP).

And they may have discarded the Apaches that came with their distribution a long time ago.

That's an excellent reason not to try to use it. If they compiled their own how am I to know how it's setup? Oh, parse the config you say? Been there, done that, currently running like hell.

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.

It sounds great, but I know how badly it works in practice. That's exactly how Bricolage works. In practice there's just too many ways to setup an Apache install. Trying to adapt to them all automatically, even with a bunch of configuration options, is an endless game of whack-a-mole. I'm determined to find something better.

-sam

In reply to Re: Re: Installation System Design for a Large Apache/mod_perl Application by samtregar
in thread Installation System Design for a Large Apache/mod_perl Application by samtregar

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.