Try using a relative path instead of an absolute one. Your scripts will do this: 
use lib '../lib';

[download]
so going to production involves pretty much a tar/untar operation; everything moves together, rather than separately. You might want to explicitly install any CPAN modules that you're using into your own lib/ directory to ensure that someone upgrading the system Perl doesn't mess you over by changing a module on you.

If you wanted to make it even neater, symlink to the production version; to change versions, alter the symlink. Also makes it really easy to drop back to a previous version if necessary. In detail:

  1. Move your software foobar-v1.0 and symlink foobar to that. Your software runs out of foobar.
  2. Install your new version by untarring it at foobar-v1.1.
  3. Delete the symlink and symlink foobar-v1.1 to foobar. The new version is now running out of foobar.
This works really nicely because you've just moved a single symlink; if you really have to fall back, you move the symlink and nothing else to revert.

In reply to Re: What is the best practice to migrate scripts from test to production by pemungkah
in thread What is the best practice to migrate scripts from test to production by Anonymous Monk

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.