Directory structure

Root directories

Specific directories designation

The above table and notes summarize the designation of some special directories regarding their writability settings.

Directory designation Path Read ACL Write ACL mkdir browse/list
Flatfile database(II) /private/drake 6 6 no no
Querystring cache(I) /private/cache 6 6 no no
Galleries /images/gallery 0 2(VI) yes 2(VI)
Private(IV) /private/ 6 6 no(IV) no
Temporary directory (V) /private/temp 6 6 yes (V) no
SQL backups /private/backup 5 4 no 5
Downloads /private/downloads 6 4 no 4
Banners directory /images/banners 0 4 no 4
Icons (ex. for content) /images/icons 0 2 no 2
Content media (ex. uploaded images) /images/ 0 2 no 2

Possible changes

Directories organization should consider the above needs; the number of directories should also be reduced as much as possible, the more we reduce the number of directories the more clearer the content will be deployed.

The user will be explained how to raise permissions using an "elevator" directory which already has the needed permissions. This will no more stop installations where it is theorically possible.

I: querystring-based caching should be provided by the server; an embedded caching mechanism could be embedded but nothing is planned until v1.0

II: flatfile databases (Gladius DB or SQLite), when active, will deploy their files in the private/drake directory (where drake is the database name)

IV: this directory should not contain any sparse file; only config.php and log.php need to be writable

V: this directory will be used to store temporary files when the system's temporary path cannot be used

Goals

The purpose of the above designations is to allow the following configurations:

The integration of an FTP client class will also enlarge our features during installation.

Related pages