In Kayuda, one of our concerns is how to minimize environmental differences between prod and staging. We use scripts to build environments and the like, but it's still not the same thing. We'd also like to only build the prod environment once, not once for each prod machine.

I just took a good look at PAR for the first time today and it looks like it would be perfect for the job. Assuming identical OSes for staging and prod, I theoretically should be able to build a PAR for my CPAN modules on staging, test it, and push it up to prod on some NFS-mounted partition that all the prod machines can see.

Anyone do this? Tried it and not liked it?

For the record, I'm talking about doing this solely to manage all the CPAN dependencies the app would have, not the actual application code. (At least, for now.) The app code has dependencies on files that cannot reasonably be served from NFS, like images and CSS and JS and the like. Maybe as a second pass.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Using PAR for a relocatable environment by dragonchild

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.