 |
        |
|
|
 |
||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
|
Installation
To install Roxen WebServer you first install the software, then connect to the web based administration interface and create the actual web or FTP sites. For each site you enable and configure the modules that are going to handle it. A basic web site only needs a small set of modules while a highly customized site that makes full usage of scripting and database needs more. To make it simpler to get started there are predefined server templates that contain the necessary modules to get a certain type of web or ftp site up and running. By choosing a server template you do not have to manually enable those modules and you get a set of modules that gives you a working site. If you already have a web site that you want to move to Roxen WebServer this should not pose much of a problem. The toughest part is usually to get all scripts to run, since there may be slight differences between different implementations of standards such as CGI, SSI or .htaccess. Some features relies on code outside of Roxen WebServer to work. The Java support requires a Java 2.0 compliant virtual machine to be installed on the server. The database supports requires database connectivity libraries. Therefore it is harder to get these functions to work and it might be necessary to install software other than Roxen WebServer itself. Installing the SoftwareRoxen WebServer consists of a Pike interpreter and Roxen WebServer itself. The software is installed either from a binary or a source package. Binary packages are precompiled for each operating system while the user has to compile the server herself when installing from a source package. Source packages are available for Unix but not for Windows. Usually the binary packages are a lot faster and easier to install. But some libraries might differ from your system in which case you are left with compiling a source distribution. The last step of the software installation is setting a username and password and then starting the server so the administration interface becomes available. Administration InterfaceThe bulk of the installation process is done through the web based administration interface. Here you create your sites and enable the modules you need. You can download additional software directly from the administration interface with the update client. The administration interface is described in the Administration interface chapter. SitesRoxen WebServer can handle any number of web or FTP sites with their own modules. A typical Roxen WebServer installation uses at least two sites, one for the administration interface itself and another for the actual web site. Each site is bound to at least one URL, through which it is possible to access the site. The URL is handled by a port within Roxen WebServer. The ports are created automatically and can be further configured on the Ports tab. Several sites may share the same port. This is always done for IP-less HTTP, when several sites share the same IP number. But it is also possible for one web site to consist of several Roxen WebServer sites. The administration interface could be given the URL http://www.my-site/admin/ and appear as part of the web site http://www.my-site.com/. How sites work is described in the Sites chapter while ports and URLs are described in the Ports chapter. MigratingMoving an existing web site to Roxen WebServer should pose no major problems, if Roxen WebServer supports all scripts that are used on the site. Usually you only have to tell Roxen WebServer where the web site is located. If scripts are used you also need to enable modules to handle the scripts. If your previous installation was using some special custom modules or similar that you for some reason can not run straight away under Roxen, a relaying solution is suggested. |
|
||||||||||
|
|
