Here are my thoughts:
  1. Install the machine that your intranet will run on. I would suggest thinking about your addressing and naming schemes, too. You could have two IP addresses for the machine, if it will be doing things as well as being your intranet server. Have the second ip address mapped to the host name "intranet" or whatever is meaningful. I assume you have an internal DNS machine. A good suggestion, if your internal network has more that 50 machines, is to have a dedicated "network management" box - this would be your internal DNS master, your DHCP sever, Radius server (if you have it), NIS master (if you use NIS), and so on. Ideally, don't make this an application server as well (so don't use this as your intranet server). It doesn't have to be a big machine - where I use to work we use an old Sun Sparcstation 10, if you are a Linux shop, any old pentium machine will do.
  2. Install the web server software. Get the latest versions of Perl, Apache, mod_perl, and anything else you need. Read instructions and install. Again, the installation and configuration of this software is not difficult, but some parts of Apache can be confusing, particularly if you are using virtual hosts. Since you want to use perl (as CGI programs), you should work out where you will locate the perl programs within your document tree. The "standard" way is to have a cgi-bin directory outside the document tree. However, if you are planning on having a lot of perl programs, you may want to consider having the cgi program within the same directory as the HTML files, to avoid confusion. You will need to set the "EXECCGI" value appropriately to allow this - by default, Apache does not allow CGI programs to be executed from any directory, unless explicitly allowed. Read the documentation on this.
  3. You may need to check the internet proxy settings on all the browser installations. A quick check - make sure none of your Windows machines have a hosts file hanging around in the C:/Windows directory (or maybe C:/Windows/system ?), and their TCP/IP network configs are right. If you are using DHCP (you are, aren't you?), then the DHCP server can set the DNS server and gateway addresses as well as allocating each machine its IP address.
  4. Consider having a second intranet server - on a second machine - as your "development and testing" platform. This is where you can make sure Perl 5.6.2 will not crash your CGI programs, or you can experiment with Mason, or whatever.

What you are going to do is not difficult or complex, just spend a day or two planning it all out first. Good change management on config files is important too - you may want to consider using some version control software on these files.

In reply to Re: How to install perl for intranet? by Maclir
in thread How to install perl for intranet? by tapesorcdz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.