Annotation of texttool-architecture/server-archimedes.tex, revision 1.3
1.1 casties 1: \subsubsection{Archimedes}
2: \label{sec:archimedes}
3:
1.2 bcfuchs 4: \paragraph{Where things are}
5: NOTE: ``CVS'' indicates that item is also avail on CVS
6: \begin{enumeration}
7: \item /docuserver/images/archimedes -- toc.cgi objects for corpus 1
8: \item /docuserver/images/archimedes/log -- log files -- error log for
9: toc.cgi; error log for search program
10: \item /usr/local/httpd/cgi-bin/toc -- toc.cgi script CVS
11: \item /usr/local/httpd/cgi-bin/toc/.toc_config -- toc.cgi
12: configuration info CVS
13: \item /usr/local/httpd/cgi-bin/toc/.toc_config/config.xml -- toc.cgi
14: configuration file (with internal DTD and inline documentation). CVS
15: \item /home/bcfuchs/bin -- some helper apps; makelemma.pl makefast.pl
16: \item /home/bcfuchs/perl/docuimages -- some helper apps; addarch.pl
17:
18:
19:
20: \end{enumeration}
21:
1.3 ! bcfuchs 22: \paragraph{collection structure}
! 23:
! 24: toc.cgi display data are grouped in ``collections''. Each collection
! 25: consists of one or more ``works''. For historical reasons, the
! 26: structure of the collection follows the unix filesystem structure: a
! 27: collection consists of a directory with one subdirectory for each
! 28: ``work'' belonging to the collection. Thus, a collection might look
! 29: something like this:
! 30:
! 31: /archimedes
! 32: /archimedes/agricola
! 33: /archimedes/baif
! 34: /archimedes/borro
! 35:
! 36: The configuration file ``config.xml'' defines the number of collections
! 37: and gives the path to the collection directory. It is assumed that all
! 38: collection directories will be stored locally.
! 39:
! 40: \paragraph{work structure ARCHIMEDES}
! 41:
! 42:
1.1 casties 43: %%% Local Variables:
44: %%% mode: latex
45: %%% TeX-master: "texttools"
46: %%% End:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>