          Installing Roxen WebServer 2.1 - the Source distribution
          +++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Observe: To avoid permission problems for the running Roxen, the
installation of Roxen should be done as the user you intend to run
Roxen as.

  1. Get the source server package.

  2. Issue the command to unpack the archive:

          .tar.gz:
               If you have GNU tar; "tar xzf Roxen-archive-name"
               If you don't have GNU tar:
               "gunzip < Roxen-archive-name| tar xf -"
          .tar.Z
               If you have GNU tar; "tar xzf Roxen-archive-name"
               If you don't have GNU tar:
               "uncompress < Roxen-archive-name| tar xf -"
          .tar
               "tar xf Roxen-archive-name"

     (where "Roxen-archive-name" is the name of the Roxen archive
     file.).

  3. Type "cd <roxen_version>" to change to the new directory. This
     directory should contain at the very least two directories:
     server (Roxen server source), pike (the Pike intepreter).

     (Where <roxen_version> is the name of the unarchived Roxen directory.)

     The directory may also contain sources for some useful libraries
     like gmp, odbc and zlib. Pike requires gmp by default, so make sure
     you have it installed or compile Pike with the configure option
     --without-gmp in 4b.

 4a. Type "make install" to install Roxen Challenger in /usr/local/roxen
     with the Pike interprenter in /usr/local/pike.

 4b. (This is an alternative method if you want to install Roxen somewhere
      else than /usr/local, or if method 4a fails. It is not
      recommended for beginners.)

     Type "./configure --prefix=<wanted_base_path_for_roxen>"
     (defaults to /usr/local, thus placing Roxen in /usr/local/roxen/)
     followed by make and make install to build the binaries and copy them
     to the correct place.

     You can later on move the 'roxen' directory that will be
     created when you type 'make install' to anywhere in your
     filesystem. Roxen does not keep any absolute paths. The 'pike'
     directory can not be moved.

     If everything worked fine and the compilation is done, type
     "cd <dir>/server" followed by "./create_configinterface". This
     creates an administration interface for the server.

     After that (still standing in the server directory) type
     "./start" to start the server and put it in the background.

     (Where <dir> is /usr/local/roxen following 4a, or
      <wanted_base_path_for_roxen>/roxen if you used 4b.)

  5. Answer the simple questions and then start you favourite webbrowser
     and point it to the configuration interface you just set up.

  6. If everything worked, configure the server, otherwise move on to the
     troubleshooting section on the roxen WWW-pages.

 Once you have installed the server, consider joining the Roxen
 mailinglist (by sending a mail to roxen-request@roxen.com, with
 Subject: subscribe).

 For more information about Roxen, read the online documentation at
 http://www.roxen.com/

----------------------------------------------------------------------------
Example installation session using the 4b route:

bash$ tar xzf roxen_2.1.tar.gz
bash$ cd roxen_2.1
bash$ mkdir solaris
bash$ cd solaris
bash$ ../configure --prefix=/usr/www

<Lots and lots of checks...>

bash$ make install

<Lots and lots of compilations...>

bash$ cd /usr/www/roxen/server
bash$ ./create_configinterface
<answer a few questions>

bash$ ./start

<Server is up and running>

----------------------------------------------------------------------------
Example installation session using the 4b route:

bash$ tar xzf roxen_2.1.tar.gz
bash$ cd roxen_2.1
bash$ make install

<Lots and lots of checks...>
<Lots and lots of compilations...>
<answer a few questions>

<Server is up and running>
