www.grootersnet.nl

Setting up Apache and Tomcat

Of course, Apache HAD already be done. Only, it was on the system disk and should be moved to another one, and webs needed to be re-organized.

First - a number of webs will be set up. That is: Apache allows this concept via the notion of "virtual webs". For this, the interface of the machine requires different IP-addresses (which has in fact nothing to do with Apache, of course), giving the router the possibility to redirect traffic to different addresses when incoming requests are on different ports. However, Apache has another possibility: same address but different name.

In the end, it will be a mix of these.

First, the structure on this disk is set up:

PUBLIC - for the public access (on port 80), named www.grootersnet.nl (this site, indeed).
PRIVATE - NOT for public access so authentication required. Luckily this can be done against the system - advisable because it's profoundly SAFE. This works - but cannot be accessed from the internet - yet
SPECIAL - When talking to a relative, who required a LOT OF room during a few month, I offered him facilities. For this kind of things, there will be this special site - on a disk of it's own. Probably there will be other small webs be hosted there for a short time - but that's not certain yet.

Done so, set this up and copied all APACHE files. After some trouble, Apache got running, So tried to re-locate Tomcat as well - which actually went Ok but after that, JSP's couldn't be handled. In the end removed and reinstalled TOMCAT which removed the problem.

Also installed a CGI script and program to monitor the progress of the Seti client. The program had a few flaws causing the script to fail: it didn't handle empty stings correctly. Since it's open source, solved that problem and returned it to the original writer.

Since the machine is intended to be a mail server as well, it would be nice if mail could be read 9end sent, eventually) by a web interface. On the sane site as the Seti-monitor, I found YetAnotherHyperMAIL - the YahMAIL package. This is also a CGI script and program, using APACHE's facility to require a valid login, which I already had installed (and working). So I moved the whole thing to PRIVATE area.

Currently testing version 1.8 (beta) in close contact with the author.

Still to do: Make PRIVATE accessible - but after setting up SSL (which is required for that, for obvious reasons)

Back to DCHP setup (2)

Forward to mail setup

Back to project description

Back home