A few years ago the bloke from Morgan Stanley gave a presentation at OSCON titled, IIRC, "One Perl to Rule Them All." The idea was that he had (he was the Perl/IT manager for the company) one canonical version of Perl that his company's developer's world wide used as *the* version for their development. That way, everyone was working off of the same basic code base quality checked at one point of inspection.
Well, I want to find out how to implement something like that on a drastically smaller scale. I have a small network of 7-9 machines on a very fast local network. I would like *all* production level stuff to be served from one app per machine (MySQL on computer, PostgreSql on another, ArcGIS on yet another... similarly, production level Perl/PHP/Pyhon/Ruby/Java on one including all the CPAN packages, etc.). Similarly, only one production web server that can serve both cgi scripts as well as mod_perl.
Of course, any remaining machines would be available for tinkering, so I can install the latest, bleading edge Perl module or Perl 5.1.11, and not bring the house down.
How do I go about implementing something like this? Esp., how do I create one Perl snapshot that all other applications on all other machines including the web server can take advantage of? I would like even PostgreSql's PL/Perl to be built off of this production quality Perl.
Guide me monks. Lead me to the light. I am assuming once I know the Perl way, I can probably apply it to Python/PHP etc. as well.
In reply to One Perl to Rule Them All by punkish
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |