FS#5876 - Lighttpd should not install to /home/lighttpd

Attached to Project: Arch Linux
Opened by tardo (tardo) - Wednesday, 22 November 2006, 02:17 GMT
Last edited by Pierre Schmitz (Pierre) - Monday, 14 July 2008, 01:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

As the above states, installing Lighttpd to it's own seperate dir (/home/lighttpd) causes problems for other packages dependent on its wwwroot, for example, packages like phpmyadmin, dokuwiki, etc, install into /home/httpd (which I believe is what apache uses). I suggest either having lighttpd install into /home/httpd or perhaps having a global _wwwroot variable somewhere so pacman can detect it.
This task depends upon
 FS#1857 - apache's DocumentRoot 

Closed by  Pierre Schmitz (Pierre)
Monday, 14 July 2008, 01:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  webservers are using /srv/http now.
Comment by Jan de Groot (JGC) - Wednesday, 22 November 2006, 07:43 GMT
IMHO the design of web packages on archlinux is completely broken. Applications like phpmyadmin and phppgadmin could get installed to /usr/share/php{my,pg}admin for example, using an alias in the apache/lighttpd/whatever configuration. /home/httpd, or /var/www like it is on most other distributions, should only contain documents placed there by users, not web application software which is under control of pacman.
Comment by tardo (tardo) - Wednesday, 22 November 2006, 19:46 GMT
I just tried using aliases, it works fine with lighttpd. The command I used for lighttpd.conf was

alias.url = ( "/phpMyAdmin/" => "/usr/share/phpMyAdmin/" )

Also had to change permissions for /usr/share/phpMyAdmin to match lighttpd.

I'm all in favor for this new method.
Comment by Roman Kyrylych (Romashka) - Wednesday, 22 November 2006, 20:44 GMT
I agree with JGC. There should be more standardization for web packages. And making them independent of specific HTTP server is absolutely necessary thing.
Comment by Christ Schlacta (aarcane) - Saturday, 13 January 2007, 12:58 GMT
I'm personally against the installing of web packages of this nature. I feel that they should be downloaded and isntalled from the website they originate from, and that including them in any distro's package manager should be avoided, as it complicates their usage and configuration, and leads to users who have no clue how to use or configure the software, and end up whining when it breaks.

just my two centavos.
Comment by Bob Fanger (NebyGemini) - Saturday, 30 June 2007, 22:30 GMT
My /var/www/ is symlinked to /home/httpd to solve this problem. Although a more clear design for this kind of packages is preferable.
But IMHO /opt/php-apps/{$pkgname} makes more sense than /usr/share because web packages do contain configuration files and some web packages may even want to create cache files dynamically.
Comment by Cesar Alcalde (noalwin) - Saturday, 01 September 2007, 12:40 GMT
It think that all http servers shouldn't be in /home. /home should be only for human users. The server packages should be in /srv according to FHS [1] or in /var/www like other distros

[1] http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM

Loading...