File Layout of TCM's web server

Apache

Apache is installed under /WWW and runs chrooted under that directory.

Its configuration files are in:

/WWW/usr/local/apache2/conf/httpd.conf
/WWW/usr/local/apache2/conf/extra/httpd-vhosts.conf

Its log files are in:

/WWW/usr/local/apache2/logs

HTML

The source files for the web server(s) are given by the httpd-vhosts.conf file. Currently:

www   /new
w6    /w6           (current web site, all from ~web/htdocs)

www.andrewjmorris.org   /u/fs1/ajm255/public_html
www.lcelastomer.org.uk  /u/fs1/mw141/lce_html

www3.tcm.phy.cam.ac.uk UCS MWS -- nothing to do with this machine

Remember that the above, and any symlinks encountered, will be interpreted in a chrooted environment, so /WWW will be prefixed.

Maintaining Files

The web server is not backed up, but ~web on TCM's main fileserver is. So ~web/htdocs should be a current copy of everything that the web server requires.

In order to optimise the serving of some common files, some files are actually placed on the server itself.

lrwxrwxrwx 1 root root   23 Jul  9 15:52 about -> /u/fs1/web/htdocs/about
lrwxrwxrwx 1 mjr  web    25 Jul  9 16:01 castep -> /u/fs1/castep/public_html
lrwxrwxrwx 1 root root   27 Jul  9 15:52 computers -> /u/fs1/web/htdocs/computers
lrwxrwxrwx 1 root root   24 Jul  9 15:52 errors -> /u/fs1/web/htdocs/errors
lrwxrwxrwx 1 root root   24 Jul  9 15:52 events -> /u/fs1/web/htdocs/events
-rw-r--r-- 1 mjr  web   518 May 29 14:29 favicon.ico
drwxr-sr-x 2 mjr  web  4096 Jul  9 15:59 fonts
-rw-r--r-- 1 mjr  web   628 Jul 10 11:31 front_page_news.html
-rw-r--r-- 1 mjr  web  1379 Jul  9 16:00 front_page_spiel.html
drwxr-sr-x 2 mjr  web  4096 Jul  9 16:28 images
lrwxrwxrwx 1 mjr  web    24 Jul  9 16:01 impact -> /u/fs1/web/htdocs/impact
drwxr-sr-x 2 mjr  web  4096 Jul 10 11:44 includes
-rwxr-xr-x 1 mjr  web  5880 Jul 10 11:12 index.html
lrwxrwxrwx 1 mjr  web    26 Jul  9 16:02 internal -> /u/fs1/web/htdocs/internal
lrwxrwxrwx 1 mjr  web    22 Jul  9 16:02 news -> /u/fs1/web/htdocs/news
lrwxrwxrwx 1 mjr  web    24 Jul  9 16:02 people -> /u/fs1/web/htdocs/people
-rwxr-xr-x 1 mjr  web  3229 Jul 10 11:09 privacy.html
lrwxrwxrwx 1 mjr  web    26 Jul  9 16:02 profiles -> /u/fs1/web/htdocs/profiles
lrwxrwxrwx 1 mjr  web    30 Jul  9 16:02 publications -> /u/fs1/web/htdocs/publications
lrwxrwxrwx 1 mjr  web    26 Jul  9 16:02 research -> /u/fs1/web/htdocs/research
-rwxr-xr-x 1 mjr  web    50 Jul 10 11:10 robots.txt
lrwxrwxrwx 1 mjr  web    15 Jul 10 11:45 sixtieth -> events/sixtieth
drwxr-sr-x 2 mjr  web  4096 Jul  9 16:03 style
lrwxrwxrwx 1 mjr  web    27 Jul  9 16:03 sw -> /u/fs1/mjr19/public_html/sw
lrwxrwxrwx 1 mjr  web    22 Jul  9 16:03 tlm -> /u/fs1/tlm/public_html
lrwxrwxrwx 1 mjr  web    27 Jul  9 16:03 vacancies -> /u/fs1/web/htdocs/vacancies

These can be maintained with web_scp by those with login access to web.tcm, and in a suitable group on it.

pc52:/u/fs1/web/htdocs$ web_scp front_page_news.html
scp front_page_news.html web:/WWW/new/front_page_news.html
front_page_news.html                          100%  625     0.6KB/s   00:00

Before using web_scp, one can preview changes by looking at w6.tcm, which takes all of its data directly from ~web/htdocs.

web:/WWW$ ls -l w6
lrwxrwxrwx 1 root root 17 May 25  2015 w6 -> /u/fs1/web/htdocs

Of course checking changes to public pages with validator.w3.org is a very good idea.