X-Git-Url: http://git.freeside.biz/gitweb/?a=blobdiff_plain;f=httemplate%2Fdocs%2Finstall.html;h=4870c7db79748bcd792a66397e8453bf41326bd3;hb=1290c097176adcd62d48b1250233d53adb4b50a5;hp=20bb168dfff633c55793ed7d84a8ff0b217b1231;hpb=6991d4986df7fb3a6c7c49b5ae1b3713e87a16c4;p=freeside.git diff --git a/httemplate/docs/install.html b/httemplate/docs/install.html index 20bb168df..4870c7db7 100644 --- a/httemplate/docs/install.html +++ b/httemplate/docs/install.html @@ -5,14 +5,18 @@

Installation

Before installing, you need: Install the Freeside distribution: @@ -57,18 +63,23 @@ Install the Freeside distribution:
  • with PostgreSQL:
     $ su postgres
    -$ createuser -P freeside
    +$ createuser -P freeside +Enter password for user "freeside": +Enter it again: +Shall the new user be allowed to create databases? (y/n) y +Shall the new user be allowed to create more new users? (y/n) n +CREATE USER
  • with MySQL:
     $ mysqladmin -u root password 'set_a_root_database_password'
     $ mysql -u root -p
     mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP on freeside.* TO freeside@localhost IDENTIFIED BY 'set_a_freeside_database_password';
    -
  • Unpack the tarball:
    gunzip -c fs-x.y.z.tar.gz | tar xvf -
    +
  • Edit the top-level Makefile:
  • Add the freeside database to your database engine:
    @@ -90,7 +101,7 @@ $ su
     $ su
     # make create-config
     
    -
  • You should run a separate iteration of Apache[-SSL] with mod_perl enabled as the freeside user. +
  • Run a separate iteration of Apache[-SSL] with mod_perl enabled as the freeside user. @@ -100,11 +111,18 @@ $ 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. +
    • 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>
      +<Directory /usr/local/apache/htdocs/freeside-asp>
       <Files ~ (\.cgi)>
       AddHandler perl-script .cgi
       PerlHandler Apache::ASP
      @@ -112,26 +130,25 @@ PerlHandler Apache::ASP
       <Perl>
       $MLDBM::RemoveTaint = 1;
       </Perl>
      -PerlSetVar Global /usr/local/etc/freeside/asp-global/
      +PerlSetVar Global /usr/local/etc/freeside/asp-global/
       PerlSetVar Debug 2
       </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
    • 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>
      +<Directory /usr/local/apache/htdocs/freeside-mason>
       <Files ~ (\.cgi)>
       AddHandler perl-script .cgi
       PerlHandler HTML::Mason
       </Files>
       <Perl>
      -require "/usr/local/apache/conf/handler.pl";
      +require "/usr/local/apache/conf/handler.pl";
       </Perl>
       </Directory>
       
      @@ -164,6 +181,11 @@ $ freeside-adduser -h /usr/local/etc $ su freeside $ bin/fs-setup username +
    • As the freeside UNIX user, run bin/populate-msgcat username to populate the message catalog, passing the username of a Freeside user you created above: +
      +$ su freeside
      +$ bin/populate-msgcat username
      +
    • freeside-queued was installed with the Perl modules. Start it now and ensure that is run upon system startup.
    • Now proceed to the initial administration of your installation.