|Don't ask to ask, just ask|
Baby step to proper packagingby mandog (Curate)
|on Aug 28, 2008 at 22:01 UTC||Need Help??|
mandog has asked for the
wisdom of the Perl Monks concerning the following question:
We have a medium sized web application that is about 40 .pl and .pm files, not counting core & CPAN modules. It is running on exactly one site. The users like it. They'd like instances running with different (and maybe overlapping) data on 2 more domains.
Our packaging is lame. We were: falsely lazy, under some pressure to “just get it done”, learning Perl, originally just doing one instance of this app and working with artistic managers. Also, the dog ate our homework
For example, only the original developer trusted the home-brewed installer. As a result people copy files by hand or (ugh!) modify production files in place. We're a tiny group, right now just me. At times we have as many as 3 people working on the project. Usually the people working on the project are new to programming, Perl and Linux.
Our dream is a full-on Debian webapp policy compliment package. Sadly, history repeats. Management is much less artistic but the world still pressures us to be falsely lazy. I've got until Tuesday 8:00am to make general infrastructure improvements. (Then the priority is filing tax reports with the IRS)
Right now, my limited goals are, in order of importance:
An example advantage of standard packaging is to be able to easily run Devel::Cover
My draft plan is:
If things, work as I plan:
I'm imagining a directory setup like:
While of course our t/ tests are getting better, I'm imagining hand testing at URLs like: