directory to anywhere in
your file system. Roxen does not keep any absolute paths.
Example installation session:
bash$ tar xzf roxen_1.2.tar.gz
bash$ cd roxen_1.2/server
bash$ ./install
Answer a few questions.
Source distribution
- Get the source server package.
- Issue the command to unpack the archive:
If you have GNU tar;
tar xzf Roxen-archive-name
- If you don't have GNU tar:
gunzip Roxen-archive-name
tar xf Roxen-archive-name
(where Roxen-archive-name is the name of the Roxen archive file.).
- Type
cd roxen_version
to change to the new directory. This directory should contain at
the very least four directories: server (Roxen server source), pike
(the Pike interpreter), extern (misc. programs used by Roxen) and
tools (misc tools). See README for more information about the
directory structure.
(Where roxen_version is the name of the unpacked Roxen
directory.)
- Type
make install
to install Roxen in /usr/local/roxen.
(If you do not wish to install roxen in
/usr/local/roxen, see "Alternative installation" below.)
- Answer the simple questions and wait for your client.
- Choose a password.
- Set up the necessary variables.
Example installation session using the above route:
bash$ tar xzf roxen_1.2.tar.gz
bash$ cd roxen_1.2
bash$ make install
Lots and lots of checks ...
Lots and lots of compilations
answer a few questions
Alternative installation:
This is an alternative method if you want to install Roxen somewhere
else than /usr/local/roxen, or if method 4 fails.
Follow the points in the normal installation, but replace 4 with
this:
- 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 file
system. Roxen does not keep any absolute paths.
- If everything worked fine and the compilation is done, type
cd dir/server
(Where dir is wanted_base_path_for_roxen/roxen)
- Start the install script by typing
./install.
Example installation session using the alternative route:
bash$ tar xzf roxen_1.2.tar.gz
bash$ cd roxen_1.2
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$ ./install
Answer a few questions.
Microsoft Windows installation
The Microsoft Windows version is distributed as a self-extracting
.EXE file, containing a graphical installation program.
- Run the self-extracting archive file and follow the instructions
given by the installation wizard. You will be prompted to select where
you want the Challenger files to be stored.
- Answer yes or no when asked if Roxen should be run as a
service. (Windows NT only)
- Challenger is started by choosing Start Roxen from the
Start menu. Once Challenger is started you can connect to the
configuration interface, that will be reachable at http://localhost:22202 given that you
run your browser on the same machine as Challenger.
Running Roxen as a console application
- Choose "Roxen console mode" from the start menu
or
- Double-click on ntroxenloader.pike where Roxen was installed.
Running Roxen as a Windows NT Service
To register the Roxen-service, run:
roxen-dir\server\bin\roxen_service.exe -install
To remove the Roxen-service, run:
roxen-dir\server\bin\roxen_service.exe -remove
You should of course replace roxen-dir with the path to the
directory where you installed Roxen.
To start or stop the the Roxen service:
- Start the "Control panel"
- Run "Services"
- Find "Roxen service" and click on start or stop
or run:
net start roxen_service
net stop roxen_service