|Don't ask to ask, just ask|
Wisdom about "packaging" or transporting Perl appsby bradcathey (Prior)
|on May 27, 2010 at 02:04 UTC||Need Help??|
bradcathey has asked for the
wisdom of the Perl Monks concerning the following question:
I'm actually seeking more wisdom than know-how. Here's the tee up:
About 5 years ago we developed a CMS built around Perl and several popular CPAN modules—at the core CGI::Application, some of it's plugins, HTML::Template, and HTML::FillInForm, to name a few. I've continued to finesse the application, adding JSON support, etc, but still never getting away from the original code and modules.
Why is the discussion of the CPAN modules necessary? Well, because of all the modules necessary to support the CMS, I've always hosted my client's sites on my server. However, we are getting pressure to compete with open source platforms like Joomla and Drupal and install it on other servers. Well, we are thinking that being dependent on all these CPAN modules, which maybe difficult to install on unfamiliar servers, could limit us.
Is there a way to package our CPAN dependent system easily on other servers that I'm not aware? The thought of rewriting the entire thing in PHP (Drupal and Joomla) seems daunting (not a big fan of PHP). It would be great to have it install like either of these, or Wordpress: upload a .tar.gz file, unpack it, and Bob's your uncle.
"The important work of moving the world forward does not wait to be done by perfect men." George Eliot