Directory structure
From Lanius CMS Wiki
Contents |
Root directories
- admin/ - webserver-published files relative to backend
- css/ - webserver-published CSS files for frontend
- editor/ - webserver-published WYSIWYG editors files (no server scripts inside)
- images/ - webserver-published multimedia files for frontend and backend
- js/ - webserver-published javascript include files for frontend and backend
- lang/ - language packages, all server-side scripts except for flag image file (flag.png)
- media/ - webserver-published user-provided multimedia files
- private/ - private directory for data, should not be published on webserver
- src/ - Lanius CMS source code, should not be published on webserver
- admin/ - admin-only source files
- adodbm_drivers/ - adoDBM database drivers
- classes/ - frontend classes source code
- components/ - components source code, no webserver-published files inside
- includes/ - Lanius CMS include files used by frontend code
- modules/ - modules source code, no webserver-published files inside
- plugins/ - plugins source code, no webserver-published files inside
- templates/ - frontend templates, should be published on webserver; contains only one server side script (index.php)
Directories designation
The below table and notes summarize the designation of some special directories regarding their writability settings.
| Designation | Path | Read group | Write group | Create dirs | Browse/list |
| Flatfile database(II) | /private/lcms | 6 | 6 | no | no |
| Querystring cache(I) | /private/cache | 6 | 6 | no | no |
| Galleries | /media/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 | /media/banners | 0 | 4 | no | 4 |
| Icons (ex. for content) | /media/icons | 0 | 2 | no | 2 |
| Content media (ex. uploaded images) | /media/ | 0 | 2 | no | 2 |
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/lcms directory (where lcms 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
VI: not currently supported
Supported hosting configurations
The purpose of the above designation is to allow (theorically) the following configurations:
- no hosting write access with any database (except flatfile) and manual config.php creation (no installation allowed)
- hosting write access on at least one directory with mkdir rights in it (permission elevator used here, installation allowed, minor limitations, flatfile database ok)
Note: Lanius CMS does not currently work with any of the above host configurations
