This file contains specialized markup tags which encode information readable
by the LON-CAPA make/build process. This is meant to be "the master file" which
encodes all necessary configuration information to the associated make process.
The format of these tags is:
<LONCAPA TYPE=type [otherparameters]>
Here are examples of all the different types of LONCAPA make/build tags.
<LONCAPA TYPE=LOCATION DIST="redhat6.2" SOURCE="modules/TexConvert/tthperl/lontex.pm" TARGET="home/httpd/lib/perl/Apache/lontex.pm" CATEGORY="handler">
<LONCAPA TYPE=DIRECTORY DIST="redhat6.2" TARGET="home/httpd/lib/perl/Apache" CATEGORY="writeable by server">
<LONCAPA TYPE=OWNERSHIP DIST="redhat6.2" CATEGORY="setuid" CHMOD="6755" CHOWN="root:root">
<LONCAPA TYPE=RPM NAME="Vendor" VALUE="Laboratory for Instructional Technology Education, Division of Science and Mathematics Education, Michigan State University.">
The NAME tags associated with TYPE=RPM are:
Data can also be attached to any LON-CAPA tag. This is especially important for files. This is shown by these three examples:
<METAGROUP>
<LONCAPA TYPE=LOCATION DIST="redhat6.2" SOURCE="modules/TexConvert/tthperl/lontex.pm" TARGET="home/httpd/lib/perl/Apache/lontex.pm" CATEGORY="handler">
<DESCRIPTION>
Handler for TeX files
</DESCRIPTION>
</METAGROUP>
<METAGROUP>
<LONCAPA TYPE=LOCATION DIST="redhat6.2" SOURCE="modules/TexConvert/tthperl/tth.so" TARGET="usr/lib/perl5/site_perl/5.005/tth.so" CATEGORY="system file">
<DESCRIPTION>
shared library file for dynamic loading and unloading of TeX-to-HTML functionality
</DESCRIPTION>
<BUILD>
modules/TexConvert/tthperl/commands
</BUILD>
<DEPENDENCIES>
../tthdynamic/tthfunc.c
../ttmdynamic/ttmfunc.c
</DEPENDENCIES>
</METAGROUP>
<METAGROUP>
<LONCAPA TYPE=LOCATION DIST="redhat6.2" SOURCE="loncom/access.conf" TARGET="etc/httpd/conf/access.conf" CATEGORY="conf">
<DESCRIPTION>
define handlers, set parameters
</DESCRIPTION>
<NOTE>
<TABLE CELLPADDING=0 CELLSPACING=0 BORDER=1>
<TR><TD><TT>lonHostID</TT></TD><TD>LON-internal HostID of this machine</TD></TR>
<TR><TD><TT>lonRole</TT></TD><TD>Role of this machine: library, access</TD></TR>
<TR><TD><TT>lonAdmEMail</TT></TD><TD>Server Administration</TD></TR>
<TR><TD><TT>lonDefDomain</TT></TD><TD>Default domain</TD></TR>
<TR><TD><TT>lonLoadLim</TT></TD><TD>Load Limit ( 100% loadavg )</TD></TR>
<TR><TD><TT>lonExpire</TT></TD><TD>Expiration for local copies in seconds</TD></TR>
</TABLE>
</NOTE>
</METAGROUP>
The METAGROUP tags for files are anticipatively limited to: NOTE, BUILD, DEPENDENCIES and DESCRIPTION.
To allow for viewing the tag information in a tabular HTML format, the make process generates doc/loncapafiles/latestinstallconfiguration.html which has the latest HTML presentation of the current LONCAPA tag configuration settings
. Alternatively, you can just view the internal tags of this HTML file.This section contains the actual LONCAPA tag information. These tags are probably not viewable with your browser and can only be seen be examining the HTML source.
lonHostID | LON-internal HostID of this machine |
lonRole | Role of this machine: library, access |
lonAdmEMail | Server Administration |
lonDefDomain | Default domain |
lonLoadLim | Load Limit ( 100% loadavg ) |
lonExpire | Expiration for local copies in seconds |
This file configures the "name space" of the Apache web server. srm.conf defines when specific perl modules should be called to handle a given request. This definition is a function of both the name of the perl module, and a specific regular expression associated with the URL, such as "^/res/.*\.page".
Here is an example entry:
<LocationMatch "^/res/.*\.page$> SetHandler perl-script PerlHandler Apache::lonpage </LocationMatch>
list elements are separated by newlines |
each list element consists of only one value; the value for lonHostID in access.conf |
list elements are separated by newlines |
each list element consists of only two subelements separated by a colon
|
only one line needs to be changed to specify a server ip address |
Example: |
just one line with the ip address of the server |