We're working on switching from using an ancient system Perl (5.8) to a modern Perl using Perlbrew and carton. Our code uses the Catalyst Web framework and runs fine with carton and perlbrew when run directly.

We're now trying to integrate it into our production server. There we use fastcgi through apache. Part of the complication is that for security reasons, we do not want the Perlbrew install to be writable by the apache/web user.

Also since Apache is invoked through init.d, sourcing a perlbrew bashrc file is more complicated

I was wondering if there are any best practices for integrating a Perlbrew/carton managed app into Apache. I'm googled and searched on Perlmonks but could not find anything appropriate.

Thanks in advance


In reply to Best practices for deploying perlbrew and carton with apache fast-cgi by dlarochelle

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.