This page provides information of use only to the System Administrator who has "root" access to the Web server.
As described in Basic Concepts, the Content Management System manages two views of the website: the Administrative Site and the Public Site. Both reside in:
All files in these directories are assigned to group "www". Content files are owned by user "nobody". Content Management System files are typically owed by user "tgm" or root.
The Content Management System expects the Apache web server to be running PHP. Apache's configuration files typically reside in:
The Apache configuration file, httpd.conf, is set up to run virtual servers for the Administrative Site and the Public Site.
Two kinds of passwords are maintained by the Content Management System: Administrative Access Passwords and a Publishing Password.
Administrative Access Passwords
The Administrative Tools directory (/admin/) is password-protected using Apache password tools. The password file is typically stored in:
Some servers place these files in a subdirectory of conf.d. If the domain name is "yoursite.com", then the passwordfile is "passwd.yoursite". Root can add new passwords using htpasswd:
htpasswd passwordfile username password
where passwordfile is the password file and username is a valid user name on the system set up to receive email at email@example.com. (Mail is automatically generated when Edit Locks are broken.)
A separate Publishing Password is required to publish the Administrative Site contents to the Public Site. This password should only be given to persons with "sign-off" responsibility for site contents, since it allows holders to post anything on the Public Site.
The Publishing Password resides (in encrypted form) in the Administrative Site directory in:
The password can be changed by the password holder using forms on the Publish page. If the current password is lost, enter a new password by deleting the pubpass.txt file and then entering the new password on the bottom of the Publish page, leaving the "Current Password" field empty.
Multiple versions of the Public Site contents are automatically kept. If users create Snapshots of the Administrative Site content, then multiple versions of the Snapshots are also kept.
All published Public versions reside in time-stamped directories in:
where "yoursite.com" is the site's domain name. The version visible to the public is linked to by the symbolic link:
A cron script checks nightly to see if there are more than 4 versions older than 34 days and, if there are, deletes them. You should plan to archive the site every 30 days. The script will not delete the version linked to by htdocs.
All Snapshot versions reside in time-stamped directories on the Administrative Site in:
A cron script checks nightly to see if there are more than 4 versions older than 34 days and, if there are, deletes them. You should plan to archive the site every 30 days.
The Search System is based on ht://Dig software, which typically resides in:
The configuration files used by the Search System typically resides in:
Two configuration files are used, one for the Administrative Site and one for the Public Site.
Be sure that the script /usr/local/htdig/bin/rundig has been edited to set TMPDIR=/tmp (or some other world-writable place) so the scripts that call rundig to automatically build the search database have permission to create temporary files.
Unused Files Persistent Store
A list of files marked as "unused" on the Edit Content page is kept in:
Log files are kept in:
Two main log files are kept:
A log of all changes made on the a.* site using the Content Management Tools. The log includes a single line for each edit event. The tab-separated columns are:
User-id, Timestamp, Action, and Additional-information.
A log of all "Email this page" mail sent. Since anyone can send virtually any message using this feature, the log contains information used (only) to track abuse. The log includes a single line for each edit event. The tab-separated columns are:
Timestamp, Requesting-IP, Name, To-email, Page-URL, and message.
Other log files might also be kept, include indexing logs for htdig indexing.