Plesk allocates resources of installed modules in its file and folder hierarchy as shown below.
|
|
This is the root directory of Plesk. Here |
||
|
|
|
This folder is meant to store everything required for module administering. Namely, this folder contains PHP, binary and image files. |
|
|
|
|
|
This folder stores back-end part of a module meant for low-level (system) operations (normally, compiled C programs). Besides binary files, this folder stores symlinks to binary utilities located in the |
|
|
|
|
This folder stores front-end part as well as resource files, e.g. HTML help files, icons displayed on navigation buttons. To see the internal structure of this folder, click here. |
|
|
|
|
This directory stores PHP files used by front-end and back-end part of the module. The directory also stores resource files of the module, e.g. PHP localization files and templates. To see the folders nested within this one, click here. |
|
|
|
|
This folder stores back-end part of a module meant for low-level operations on the system (normally, compiled C programs) that should be executed with setuid root privileges. The directory also contains a setuid root wrapper utility meant for this task. To see the internal structure of this folder, click here. |
|
|
|
|
This folder contains the configuration file of Apache server that runs Plesk. The folder also can contain special files (one for an individual module) that modify this configuration for a certain module. To see the internal structure of this folder, click here. |
|
|
|
This folder is meant to store auxiliary files and components of Plesk – log files, SSL certificates, etc. In case of modules, this folder can contain the uninstall script for a module wrapped into a SH distribution package. |
|