MiniVend pages are
NOT in normal
HTML space. They are contained in the
catalog directory. Each individual catalog must have its own base directory. The catalog
directory has this structure by default:
- catalog.cfg
-
File containing configuration directives for this catalog. (Subcatalogs
have differing information in a file named for the subcatalog.)
- config
-
Directory that will be read when directives are set with the <filename notation. For example, the file
config/static.pages
will be read when the directive
StaticPage <static.pages
is encountered in the catalog.cfg file.
This directory also contains template information used with the makecat
program.
- error.log
-
File which contains catalog-specific errors.
Check this file when something doesn't work right.
It is also where any syntax errors in embedded Perl code will be shown.
- etc
-
Directory that contains logs, order profiles, and other information. If the ScratchDir directive is not redefined (it is set to the directory
tmp in the simple demo) then search overflow files and cache files will be
based there as well.
- pages
-
Directory that contains the pages of your catalog. This can be considered
to be the ``document root'' of the catalog. Pages contained therein are
called with the path information after the script name -- i.e.
/cgi-bin/simple/products/gold will call the page in the file pages/products/gold.html.
- products
-
Directory containing database source files, including the special MiniVend
databases shipping.asc, accessories.asc, pricing.asc (and other shipping
database files)
- reconfig
-
A script file, which when executed, will cause the catalog.cfg file to be re-read and the catalog configuration to change. If errors occur, the catalog will stay with its old/previous configuration. This script is set up by the makecat program, but may require editing if you deviate from the standard MiniVend configuration. It operates by executing the link program that is contained in the
CGI directory and passing the proper parameters through the environment.
- session
-
Directory which contains session files when
DBM sessions are not in use.
- session.gdbm (or session.db)
-
The
GDBM or DB_File session database file. This is a
DBM database that contains the user sessions.
- tmp
-
In the simple demo, this is where the cache and search paging files are
placed because of the ScratchDir definition.