Talk:Web application package guidelines
Change file system layout
If you got more than one instance of a particular webapp running on your machine the configuration files and variable data files will conflict. We should consider the Gentoo approach:
- Install a webapp to /usr/share/webapps/$pkgname or /usr/lib/webapps/$pkgname
- Use a tool like webapp-config to clone instances.
Mmh (talk) 18:44, 6 August 2013 (UTC)
The multi-instance approach is out of scope for the Arch package guidelines, as it is about packaging a single application at a time.
A safe way of hosting web applications requires user separation and handling many files (configurations, potential symlinks to writable locations, etc.).
As noone has shown interest in working on a tool similar to Gentoo's webapp-config for Arch yet, the current focus lies on making single-app setups as safe as possible to use.
However, this doesn't mean, that such a thing couldn't be achieved in a similar fashion (e.g. using systemd-nspawn(1) or portablectl(1), or in manual setups).
Davezerave (talk) 14:45, 13 April 2019 (UTC)
FHS
Where in the FHS does it say that /etc/webapps or /usr/share/webapps is an actual directory?
There's no mention of it. The only mention of these directories seem to be on *archlinux.org sites.
EDIT: It seems that Gentoo also does this, so why must webapps be installed to these directories and not /{etc,usr/share}/$pkgname?
Grawlinson (talk) 08:35, 29 March 2021 (UTC)
- This is probably more due to unwritten convention/rule, not because there is a specific rule (in regards to the
webapps/
dir). I assume, that at some point packagers deemed it necessary to distinguish the web applications from those that are not exposed to the outside world by a web server also on a filesystem level. - Note: The reference to FHS is there, because there is an implicit and very important distinction between data, configuration and state directories, which is a completely separate topic from our
webapps/
namespace. - Davezerave (talk) 08:46, 29 March 2021 (UTC)