XS Directory Layout: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 8: Line 8:
* 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 notes:
=Language specific=

* Java
Java
** Follow paths indications and recommendations from the [http://www.debian.org/doc/packaging-manuals/java-policy/ Debian Java Policy]
* Follow paths indications and recommendations from the [http://www.debian.org/doc/packaging-manuals/java-policy/ Debian Java Policy]

Revision as of 20:25, 24 March 2008

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