Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What are your limitations for installing web apps? Can you log into the machine? Are all of the the machines running the same thing? Are the people installing the web apps co-workers or random people from the general public? Are the people installing this sysadmins, programmers, web managers, or something else? Do you install by distributed an archive or checking out from source control?</p> <p>For most of my stuff, which involves sysadmins familiar with Perl installing in control environments, I just use <a href="http://search.cpan.org/dist/ExtUtils-Makemaker" rel="nofollow noreferrer">MakeMaker</a>. It's easy to get it to do all the things you listed if you know a little about <code>MakeMaker</code>. If you want to know more about that, ask a another question. ;) <a href="http://search.cpan.org/dist/Module-Build" rel="nofollow noreferrer">Module::Build</a> is just as easy, though, and the way to go if you don't already like using <code>MakeMaker</code>.</p> <p><code>Module::Build</code> would be a good way to go to handle lots of different situations if the people are moderately clueful about the command line and installing software. You'll have a lot of flexibility with <code>Module::Build</code>, but also a bit more work. And, the <code>cpan</code> tool (which comes with Perl), can install from the current directory and handle dependencies for you. Just tell it to install the current directory:</p> <pre><code> $ cpan . </code></pre> <p>If you only have to install on a single platorm, you'll probably have an easier time making a package in the native format. You could even have <code>Module::Build</code> make that package for you so the developers have the flexibility of <code>Module::Build</code>, but the installers have the ease of the native process. Sticking with <code>Module::Build</code> also means that you could create different packages for different platforms from a single build tool.</p> <p>If the people installing the web application really have no idea about command lines, CPAN, and other things, you'll probably want to use a packager and installer that doesn't scare them or make them think about what is going on, and can accurately report problems to you automatically.</p> <p>As Dave points out, using a real CPAN mirror always gets you the latest version of a module, but you can also make your own "fake" CPAN mirror with exactly the distributions you want and have the normal CPAN tools install from that. For our customers, we make "CPAN on a CD" (although thumb drives are good now too). With a simple "run me" script everything gets installed in exactly the versions they need. See, for instance, my http://www.slideshare.net/brian_d_foy/mycpan-lapm-september-2007">Making my own CPAN talk if you're interested in that. Again, consider the audience when you think about that. It's not something you'd hand to the general public.</p> <p>Good luck, :)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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