A Woof! application installation consists of a standard directory structure described below under the installation directory specified for the installer script.
This directory and its subdirectories contain all the files that are publicly accessible through the Web server. This includes the scripts that interface Woof! with the Web server as well as static resources like images. For example, the CGI script resides in this directory. Generally, files within this directory tree will be served directly by the Web server without invoking any Woof! code.
This directory is the root of the directory tree containing all CSS stylesheets referenced by the application code. See Locating static resources for how stylesheets are located.
This directory is the root of directory tree containing all images referenced by the application code. See Locating static resources for how images are located.
This directory contains the code for Woof! itself and any supporting libraries that may be required by Woof!. This directory is not present with the BowWow server as the relevant bits are included in the BowWow server itself.
This directory contains various utility scripts for generating application stubs, documentation and so on. Like the lib directory, this directory is not present with the BowWow server as the server subsumes the functionality.
This directory is the root of directory tree containing all application code.
The bulk of the application code, including the controller classes and view templates reside in this directory tree. When modules or namespaces are in use, each subdirectory in the tree corresponds to a module or namespace component. All controllers defined in that namespace are located in that subdirectory. Additionally, a subdirectory calls views within that module subdirectory contains the view templates specific to those controllers.
This directory contains all configuration files.
Depending on the configuration settings, this directory may be used for temporary files such as error logs and session files.