in reply to What is the best practice to migrate scripts from test to production

Try using a relative path instead of an absolute one. Your scripts will do this:
use lib '../lib';
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.
  • Comment on Re: What is the best practice to migrate scripts from test to production
  • Download Code