Difference between revisions of "Web application package guidelines"

From ArchWiki
Jump to: navigation, search
m (add ring template)
(there should be no symlinks; /var/ is useless for webapps)
 
(9 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
[[Category:Package development]]
 
[[Category:Package development]]
{{Package Guidelines}}
+
{{Accuracy|The file system layout is insufficient for more than one instance of a webapp.}}
{{stub}}
+
{{Package guidelines}}
This page describes how to package web application which tends to install into /srv/http. (For example packages written in php)
+
 
 +
This page describes how to package web application.
  
 
==Directory structure==
 
==Directory structure==
 
 
Layout example:
 
Layout example:
  
* /etc/webapps/$pkgname
+
* {{Ic|/etc/webapps/''$pkgname''}}
* /etc/webapps/$pkgname/apache.example.conf
+
* {{Ic|/usr/share/webapps/''$pkgname''}}
* /etc/webapps/$pkgname/nginx.example.conf
+
* /etc/webapps/$pkgname/other-web-server.example.conf
+
* /usr/share/webapps/$pkgname
+
* /var/... (according to generic FHS conventions)
+
 
+
/var and /etc/ files and/or directories should be symlinked into /usr/share/webapps/$pkgname.
+
 
+
/etc/webapps/$pkgname/ should contain some examples which helps to setup web-server to run this web application.
+

Latest revision as of 19:11, 8 July 2016

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: The file system layout is insufficient for more than one instance of a webapp. (Discuss in Talk:Web application package guidelines#)
Package creation guidelines

CLRCrossEclipseFree PascalGNOMEGoHaskellJavaKDEKernelLispMinGWNonfreeOCamlPerlPHPPythonRubyVCSWebWine

This page describes how to package web application.

Directory structure

Layout example:

  • /etc/webapps/$pkgname
  • /usr/share/webapps/$pkgname