Step 1. Making up the hierarchy of folders

If you are going to build an installation package for a web application, making up the hierarchy of folders is a good point to start. This hierarchy should begin with the system root and look as follows: /<plesk_root_dir>/var/cgitory/….

The /cgitory folder is the root of Application Vault. The application's main folder nested within should have a name formatted as follows:

<application_name>-<product_version>-<release_version>

The <application_name> section stands for the name of the application. This section should fully match with the name of the application specified in the info.xml file. Allowed are all literals and digits, spaces are inadmissible. The length of the section is not restricted.
The <product_version> section indicates the current version of the application. It can contain literals, digits, and 'dot' delimiters. The length of the section is not restricted.
The <release_version> section is used to indicate the version of the current release. Allowed are literals, digits, and dots. The length of the section is not restricted.
These sections should be delimited with the '-' character. There should not be any spaces between the sections and their delimiters. The length of the application folder name is unlimited.

Here is the example of a valid application folder:

phpAds-2.0.5-7512

phpBB-2.0.17-7118

phpBook-1.50-8011

The application folder can contain up to seven subfolders as follows:


	`/<application_name>-<product_version>-<release_version>`
		`/apps`
		`/docs`
		`/screenshots`
		`/forms`
		`/scripts`
		`/uninstall`
		`/info`

Please note: all folder names are fixed and given in the lower case.

It does not matter in what order these folders follow one another. Moreover, if some files of the web application are missing, the relevant folder can be missing in the installation package too. If the application's folder is added some extra subfolders, the installation package is considered valid anyway. Application Vault will copy these extra folders to AV Repository, but the further use of resources stored in such extra folders is the sole responsibility of the developer.

Thus, this step should result in the hierarchical structure of empty folders arranged as described above and having fixed names.

NEXT >>