ibexa

Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.

Directory structure

The eZ publish root directory contains multiple subdirectories. Each subdirectory is dedicated to a specific part of the system and contains a collection of logically related files. The following table gives an overview of the main eZ publish directories.

Directory

Description

bin

The "bin" directory contains various PHP, Perl and shell scripts. For example, it contains the "clearcache" script which can be used to clear all eZ publish caches from within a system shell. The scripts are mainly used for manual maintenance.

cronjobs

The "cronjobs" directory contains miscellaneous scripts for automated periodical maintenance.

design

The "design" directory contains all design related files such as templates, images, stylesheets, etc.

doc

The "doc" directory contains documentation and change logs.

extension

The "extension" directory contains eZ publish plugins. The extension system of eZ publish allows external code to plug in and coexsit with the rest of the system. By using extensions it is possible to create new modules, datatypes, template operators, workflow events and so on.

kernel

The "kernel" directory contains all the kernel files such as the core kernel classes, modules, views, datatypes, etc. This is where the core of the system resides. Only experts should tamper with this part.

lib

The "lib" directory contains the general purpose libraries. These libraries are collections of classes that perform various low level tasks. The kernel makes use of these libraries.

packages

The "packages" directory contains the bundled packages (themes, classes, templates, etc.) that can be installed using either the setup wizard or the administration interface.

settings

The "settings" directory contains dynamic, site specific configuration files.

share

The "share" directory contains static configuration files such as codepages, locale descriptions, translations, icons, etc.

support

The "support" directory contains the source code for additional applications that can be used to do various advanced tasks. For example, it contains the "lupdate" program that can be used to create and maintain eZ the translation files.

update

The "update" directory contains various scripts that should be used when an eZ publish installation is being upgraded.

var

The "var" directory contains cache files and logs. It also contains actual content that doesn't go into the database (images and files). The size of this directory will most likely increase as the system is being used.

Balazs Halasy (18/01/2005 1:33 pm)

Balazs Halasy (25/04/2005 7:54 am)


Comments

  • database

    Can I recuperate the database content from update's files