Peter Hintjens' Htmlpp was used to generate the HTML code. You need to install Htmlpp on your Linux system to be able to use the Htmlpp source files to generate the CLUE web site. The Htmlpp documentation is comprehensive and a great resource. Refer to the Htmlpp HTML documentation for installation instructions.
Htmlpp is a Perl program, so it needs the Perl Interpreter to run. Chances are good that your Linux system already has Perl installed. To test whether Perl is installed, type 'perl -v' at the Linux command line. You should see similar output
$ perl -v
This is perl, version 5.004_04 built for i586-linux
Copyright 1987-1997, Larry Wall
Perl may be copied only under the terms of either the
Artistic License or the GNU General Public License,
which may be found in the Perl 5.0 source kit.
If not, click on the Perl link above for more information about downloading and installing Perl.
You may want to preview the generated HTML pages. You can preview them using an HTML browser, such as Netscape Communicator. You can view a file just by opening it using the FILE menu in Communicator. Another way to view the HTML pages is to serve them through an Apache web server (httpd). Most Linux distributions will install the Apached web server when you load your Linux system. If you do not have the Apache web sever installed, refer to the Apache link above.
There are several ways to determine if you are running Apache on your Linux system. The easiest is to attempt to connect to it using an HTML browser. Try to connect to one of the following URLs.
The above links may not prove reliable if your Apache web server is not configured correctly. Another way to test for the Apache web server is to grep for the 'httpd' process. The 'httpd' is the http daemon, i.e., the Apache web server. If you see there are httpd severs running (see output below), then Apache is installed.
$ ps -aux | grep httpd
nobody 82 0.0 0.4 1080 600 ? S May 29 0:00 /usr/sbin/httpd
nobody 83 0.0 0.4 1056 584 ? S May 29 0:00 /usr/sbin/httpd
If you want to view the CLUE site using your local Apache web server, you will need to copy the generated paged to the correct directory. The default directory for this is specified in the Apache 'srm.conf' file. This file should be in /var/lib/httpd/conf or /var/lib/apache/conf. In the 'srm.conf' file, the 'DocumentRoot' specifies the location to put HTML files. Below is the 'DocumentRoot' portion of the 'srm.conf' file.
# 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 /var/lib/httpd/htdocs
So, to view the CLUE site using your local Apache web server, you would build to CLUE web site pages (see Step Two) and then copy all the generated HTML files in to the directory specified in the 'DocumentRoot' portion of your Apache srm.conf file. After you have copied the files, then you can access http://localhost to preview the CLUE site.
Once you have installed Htmlpp and Perl (if necessary), you need to download the Htmlpp source code files that generate the CLUE web site. There are two files used by Htmlpp to build the CLUE web site. The first file, clue.def, contains site definitions. The HTML code that dictates the style of each page and the navigation bars at the bottom of each page are in the clue.def file. The second file, clue.htp contains the source for each of the pages.
Refer to the Htmlpp manual for detailed information about the Htmlpp commands contained in the 'clue.htp' and 'clue.def' files.
Make sure that the clue.htp and clue.def file are contained in the same directory. Also make sure that you have htmlpp installed properly (see Htmlpp documentation for installation instructions). You are now ready to build the CLUE web site. To build it, just execute the htmlpp command using the 'clue.htp' file as input. You should see similar output as below:
$ htmlpp clue.htp
Htmlpp - a HTML pre-processor V4.2a
This is free software and may be freely modified and distributed.
Copyright (c) 1996-98 iMatix Corporation - http://www.imatix.com
htmlpp I: processing clue.htp...
htmlpp I: pass 1 through clue.htp...
htmlpp I: pass 2 through clue.htp...
htmlpp I: pass 3 through clue.htp...
htmlpp I: pass 4 through clue.htp...
htmlpp I: final pass through clue.htp...
htmlpp I: creating ./newsletters.html... 99 lines, 3993 bytes
htmlpp I: creating ./meetingInfo.html... 77 lines, 3295 bytes
htmlpp I: creating ./presentations.html... 66 lines, 2303 bytes
htmlpp I: creating ./resources.html... 112 lines, 4654 bytes
htmlpp I: creating ./volunteers.html... 123 lines, 4353 bytes
htmlpp I: creating ./siteDevelopment.html... 79 lines, 3956 bytes
htmlpp I: creating ./download.html...htmlpp I: 746 lines processed
This will generate all the CLUE web pages. Now you can make changes to your copy of clue.htp or clue.def to make improvements to the site. You can submit your changes to the clue.htp and clue.def files to the webmaster.
There are only a few images used on the CLUE site. You can download the tar.gz file here. You should gunzip and untar this file in the same directory where you built the CLUE web site. If you are using your local Apache server, then you should gunzip and untar this file in the 'DocumentRoot' directory (see Step One for details on how to locate the 'DocumentRoot' directory. To gunzip and untar the files, exeute the 'tar' command with the zxvf options (z = gunzip; x = xtract files; v = verbose; f = tar archive file):
$ tar zxvf images.tar.gz
images/clueLogo.jpg
images/tux.gif
Email the webmaster if you have questions about building a local copy of the CLUE web site.
|