in reply to How to manage the transfer of large Perl environments from one network to another

"...more system administrator-related..."

Ugly scenario. Probably it might be easier to clone the box using rsync and give it a new IP and hostname and forget about all the cruel details?

Some hints for the future: In the last company i was with we had a default setup for SLES that needed about 15m to install in a virtual machine. We had at least 4 machines for each customer: customer_dev, customer_test, customer_prod_01 and customer_prod_02. All Perl stuff installed with perlbrew. Development, testing and deployment then works like a charm. We had some hundred machines with a setup like this.

Best regards, Karl

«The Crux of the Biscuit is the Apostrophe»

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

  • Comment on Re: How to manage the transfer of large Perl environments from one network to another
  • Download Code

In Section Seekers of Perl Wisdom