X-Git-Url: http://git.freeside.biz/gitweb/?p=freeside.git;a=blobdiff_plain;f=httemplate%2Fdocs%2Finstall.html;h=0217c9085553f88678f4883a8493c35cd11e405d;hp=f2db59f88668f06f6a8dd10c74c60d3ab2ff6363;hb=72a65ceaa28155e8c1c3c1328dd76587b35e089a;hpb=edda09a317f5dfef05fb8906f28531ec6f4b0927 diff --git a/httemplate/docs/install.html b/httemplate/docs/install.html index f2db59f88..0217c9085 100644 --- a/httemplate/docs/install.html +++ b/httemplate/docs/install.html @@ -3,23 +3,28 @@

Installation

+Note: Install Freeside on a firewalled, private server, not a public (web, RADIUS, etc.) server.

Before installing, you need: Install the Freeside distribution: @@ -89,38 +115,56 @@ $ su
  • Run make aspdocs -
  • Copy aspdocs/ to your web server's document space. -
  • Create a Global directory, such as /usr/local/etc/freeside/asp-global/ -
  • Copy htetc/global.asa to the Global directory. +
  • Copy aspdocs/ to your web server's document space: +
    +cp aspdocs /usr/local/apache/htdocs/freeside-asp
    +
    +
  • Create a Global directory, such as /usr/local/etc/freeside/asp-global/: +
    +mkdir /usr/local/etc/freeside/asp-global/
    +chown freeside /usr/local/etc/freeside/asp-global/
    +
    +
  • Copy htetc/global.asa to the Global directory: +
    +cp htetc/global.asa /usr/local/etc/freeside/asp-global/global.asa
    +
  • Configure Apache for the Global directory and to execute .cgi files using Apache::ASP. For example:
    -<Directory /usr/local/apache/htdocs/freeside-asp>
    -<Files ~ (\.cgi)>
    -AddHandler perl-script .cgi
    +PerlModule Apache::ASP
    +<Directory /usr/local/apache/htdocs/freeside-asp>
    +<Files ~ (\.cgi|\.html)>
    +SetHandler perl-script
     PerlHandler Apache::ASP
     </Files>
     <Perl>
     $MLDBM::RemoveTaint = 1;
     </Perl>
    -PerlSetVar Global /usr/local/etc/freeside/asp-global/
    +PerlSetVar Global /usr/local/etc/freeside/asp-global/
    +PerlSetVar Debug 2
    +PerlSetVar RequestBinaryRead Off
     </Directory>
     
    -
  • NOTE: Mason support is still a bit buggy in the 1.4.0 prereleases. This will be fixed before 1.4.0. You have been warned.
  • Run make masondocs -
  • Copy masondocs/ to your web server's document space. -
  • Copy htetc/handler.pl to your web server's configuration directory. -
  • Edit handler.pl and set an appropriate data_dir, such as /usr/local/etc/freeside/mason-data +
  • Copy masondocs/ to your web server's document space. (For example: /usr/local/apache/htdocs/freeside-mason) +
  • Copy htetc/handler.pl to /usr/local/etc/freeside +
  • Edit handler.pl and: +
      +
    • set an appropriate comp_root, such as /usr/local/apache/htdocs/freeside-mason +
    • set an appropriate data_dir, such as /usr/local/etc/freeside/masondata +
    +
  • Configure Apache to use the handler.pl file and to execute .cgi files using HTML::Mason. For example:
    -<Directory /usr/local/apache/htdocs/freeside-mason>
    -<Files ~ (\.cgi)>
    -AddHandler perl-script .cgi
    +PerlModule HTML::Mason
    +<Directory /usr/local/apache/htdocs/freeside-mason>
    +<Files ~ (\.cgi|.html)>
    +SetHandler perl-script
     PerlHandler HTML::Mason
     </Files>
     <Perl>
    -require "/usr/local/apache/conf/handler.pl";
    +require "/usr/local/etc/freeside/handler.pl";
     </Perl>
     </Directory>
     
    @@ -131,29 +175,35 @@ require "/usr/local/apache/conf/handler.pl";
  • Restrict access to this web interface - see the Apache documentation on user authentication. For example, to configure user authentication with mod_auth (flat files):
     <Directory /usr/local/apache/htdocs/freeside-asp>
    -PerlSetVar Global /usr/local/etc/freeside/asp-global/
     AuthName Freeside
     AuthType Basic
     AuthUserFile /usr/local/etc/freeside/htpasswd
     require valid-user
     </Directory>
     
    -
  • Create one or more Freeside users (your internal sales/tech folks, not customer accounts). These users are setup using using Apache authentication; they're not UNIX user accounts. For example, using mod_auth (flat files): +
  • Create one or more Freeside users (your internal sales/tech folks, not customer accounts). These users are setup using using Apache authentication, not UNIX user accounts. For example, using mod_auth (flat files):
    • First user:
      $ su
      -$ freeside-adduser -h /usr/local/etc/freeside/htpasswd -c /usr/local/etc/freeside/secrets username
      +$ freeside-adduser -c -h /usr/local/etc/freeside/htpasswd username
    • Additional users:
      $ su
      -$ freeside-adduser -h /usr/local/etc/freeside/htpasswd /usr/local/etc/freeside/secrets username
      +$ freeside-adduser -h /usr/local/etc/freeside/htpasswd username
    - (using other auth types, add each user to your Apache authentication yand then run: freeside-adduser /usr/local/etc/freeside/secrets username -
  • As the freeside UNIX user, run bin/fs-setup username to create the database tables, passing the username of a Freeside user you created above: + (using other auth types, add each user to your Apache authentication and then run: freeside-adduser username +
  • As the freeside UNIX user, run freeside-setup username to create the database tables, passing the username of a Freeside user you created above: +
    +$ su freeside
    +$ freeside-setup username
    +
    + Alternately, use the -s option to enable shipping addresses: freeside-setup -s username +
  • As the freeside UNIX user, run bin/populate-msgcat username (in the untar'ed freeside directory) to populate the message catalog, passing the username of a Freeside user you created above:
     $ su freeside
    -$ bin/fs-setup username
    +$ cd /path/to/freeside/
    +$ bin/populate-msgcat username
     
    -
  • freeside-queued was installed with the Perl modules. Start it now and ensure that is run upon system startup. +
  • freeside-queued was installed with the Perl modules. Start it now and ensure that is run upon system startup (Do this manually, or edit the top-level Makefile, replacing INIT_FILE with the appropriate location on your systemand QUEUED_USER with the username of a Freeside user you created above, and run make install-init)
  • Now proceed to the initial administration of your installation.