XS Directory Layout: Difference between revisions
Jump to navigation
Jump to search
(New page: The base rule is to follow Debian's approach to LSB layout, called the [http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html Filesystem Hierarchy Standard FHS] while we retain some...) |
RafaelOrtiz (talk | contribs) mNo edit summary |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| ⚫ | |||
{{OLPC}} |
|||
[[Category:Software]] |
|||
[[Category:Developers]] |
|||
[[Category:SchoolServer]] |
|||
| ⚫ | |||
* Code should go to /usr (lib o bin) |
* Code should go to /usr (lib o bin) |
||
| Line 8: | Line 14: | ||
* For webapps in scripting languages /var/www/<appname> can host the code, and http://<hostname>/<appname> will normally be the entry point |
* For webapps in scripting languages /var/www/<appname> can host the code, and http://<hostname>/<appname> will normally be the entry point |
||
Language specific |
=Language specific= |
||
* Java |
|||
'''Java''' |
|||
| ⚫ | |||
| ⚫ | |||
'''Python''' |
|||
*[http://www.debian.org/doc/packaging-manuals/python-policy/ Debian Python Policy]. |
|||
'''PHP''' |
|||
*[http://webapps-common.alioth.debian.org/draft-php/html/ch-about.html Debian PHP Policy Draft] |
|||
Latest revision as of 05:00, 4 December 2008
This page is monitored by the OLPC team.
The base rule is to follow Debian's approach to LSB layout, called the Filesystem Hierarchy Standard FHS while we retain some freedom to override FHS where it makes sense. In simple terms this means that
- Code should go to /usr (lib o bin)
- Configuration must land in /etc
- /var/lib is for permanent data storage (database files, for example)
- The use /var/cache and /var/tmp should be obvious ;-)
- Logs to /var/log
- For webapps in scripting languages /var/www/<appname> can host the code, and http://<hostname>/<appname> will normally be the entry point
Language specific
Java
- Follow paths indications and recommendations from the Debian Java Policy
Python
PHP