base_server:
Contains the server core Pike code: API, CIF., etc. Newbies should not modify these files.
bin:
First binary code that is run when you use the start script. There are also some Pike scripts running as CGIs and without Caudium API.
caudium-images:
This directory contains Caudium static images from the Caudium Group, such as the "powered by" series.
config_actions:
These are files used in the Action tab on the CIF.. You may use some of these functions in your code.
etc:
Caudium includes files used by the Caudium core and its modules. For example, it contains .html files for error messages. Two directories are important for a module developer:
fonts:
Contains some compatibility fonts with some older versions. The new directory is nfonts.
languages:
Some basic language translations for time/date.
lib:
Some of the C code used to speed Caudium up. This code is a set of dynamic libraries (.so).
modules:
Contains Caudium modules. These are all the modules you see when you click Add Module after you have selected one of your servers in the CIF.. Browsing this directory will be useful to understand Caudium.
more_modules:
Some modules that meet a specific need, are not up-to-date, or are humorous.
nfonts:
Fonts for graphical things like <gtext> and <gbutton>.
You can have several types of properties like bold or italic for the same font name.
Perl:
Needed to run Perl scripts within Caudium. At the time of writing this document, Perl support is broken, and we will be pleased to get help on this issue.
protocols:
Contains protocol modules (for handling HTTP, FTP and the like).
server_templates:
The templates you can choose from when you create a new a virtual server.
unfinished_modules:
For modules in development.