Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat's the best system for installing a Perl web app?
    text
    copied!<p>It seems that most of the installers for Perl are centered around installing Perl modules, not applications. Things like ExtUtils::MakeMaker and Module::Build are very well suited for modules, but require some additional work for Web Apps.</p> <p>Ideally it would be nice to be able to do the following after checking out the source from the repository:</p> <ul> <li>Have missing dependencies detected</li> <li>Download and install dependencies from CPAN</li> <li>Run a command to "Build" the source into a final state (perform any source parsing or configuration necessary for the local environment).</li> <li>Run a command to install the built files into the appropriate locations. Not only the perl modules, but also things like template (.tt) files, and CGI scripts, JS and image files that should be web-accessible.</li> <li>Make sure proper permissions are set on installed files (and SELinux context if necessary).</li> </ul> <p>Right now we have a system based on <strong>Module::Build</strong> that does most of this. The work was done by done by my co-worker who was learning to use <strong>Module::Build</strong> at the time, and we'd like some advice on generalizing our solution, since it's fairly app-specific right now. In particular, our system requires us to install dependencies by hand (although it does detect them).</p> <p>Is there any particular system you've used that's been particularly successful? Do you have to write an installer based on <strong>Module::Build</strong> or <strong>ExtUtils::MakeMaker</strong> that's particular to your application, or is something more general available?</p> <p><strong>EDIT:</strong> To answer brian's questions below:</p> <ul> <li>We can log into the machines</li> <li>We do not have root access to the machines</li> <li>The machines are all (ostensibly) identical builds of RHEL5 with SELinux enabled</li> <li>Currently, the people installing the machines are only programmers from our group, and our source is not available to the general public. However, it's conceivable our source could eventually be installed on someone else's machines in our organization, to be installed by their programmers or systems people.</li> <li>We install by checking out from the repository, though we'd like to have the option of using a distributed archive (see above).</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload