https:///weradocs/WeraDesk_Apache.shtml Last update:

WeraDesk Web Interface Documentation - Apache Web Server

The Apache WebServer must be configured and started on the Linux machine controlling the WERA to enable the web-based WeraDesk interface. Depending on the allow/deny rules, WeraDesk can be accessed by any web browser. Javascript (on the Web Browser side) is required to calculate 'Maximum Range' and 'Data Acquisition Time' dynamically. Do not enter values into these two fields. To be able to show the lowest line of the WeraDesk Status Page correctly, Apache Server Side Includes must be configured and enabled. This is the default for the SuSE 8.1 Professional Linux distribution.

The Apache WebServer's configuration file is /etc/httpd/httpd.conf . Edit the following parameters to configure the WebServer's name [myhost.mydomain] and accessibility (this may be different within your Linux distribution, e.g. SuSE 8.1 enters 'DocumentRoot' and 'myhost.mydomain' automatically during installation): 


# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
#ServerName ifmpc143.ifm.uni-hamburg.de
ServerName myhost.mydomain

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/srv/www/htdocs"
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/srv/www/htdocs"> 
#
# Controls who can get stuff from this server.
#
    Order deny,allow
    deny from all
#   allow from .ifm.uni-hamburg.de
    allow from .mydomain

The following parameters configure access to WeraDesk and the cgi-script by ~user mapping, so WeraDesk can be accessed at
http://myhost.mydomain/~wera/WeraDesk.html
[configure in /etc/httpd/httpd.conf or /etc/httpd/suse_public_html.conf (SuSE 8.1)]: 

#
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
#
<IfModule mod_userdir.c> 
    UserDir public_html
</IfModule> 
#
# Control access to UserDir directories.  The following is an example
# for a site where these directories are restricted to read-only.
#
<Directory /home/*/public_html> 
    AllowOverride FileInfo AuthConfig Limit
    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
    <Limit GET POST OPTIONS PROPFIND> 
     Order deny,allow
     deny from all
#    allow from .ifm.uni-hamburg.de
     allow from .mydomain
    </Limit> 
    <LimitExcept GET POST OPTIONS PROPFIND> 
     Order deny,allow
     deny from all
#    allow from .ifm.uni-hamburg.de
     allow from .mydomain
    </LimitExcept> 
</Directory> 
#
# Control access to User scripts.
#
<Directory /home/*/public_html/cgi-bin> 
        Options ExecCGI
        SetHandler cgi-script
</Directory>

To make /home/wera/public_html accessable for Apache, enter from user root: 

chmod 711 /home/wera

Then from user wera create the directories (if they don't already exist) : 

mkdir /home/wera/public_html
mkdir /home/wera/public_html/cgi-bin
mkdir /home/wera/etc

Now you can unpack the weradocs_xxx.tar.gz package:
(assuming you have the archive mounted at /mnt/cdrom) 

cd /home/wera
tar -xvzf /mnt/cdrom/weradocs_xxx.tar.gz

To make .html pages accessable to apache, execute the following commands after installing files to /home/wera/public_html : 

cd /home/wera
chmod 755 public_html
cd public_html
chmod -R 755 *

Comments to: gurgel@ifm.uni-hamburg.de (Klaus-Werner Gurgel)