Arch Linux

Here is how I have modified my PKGBUILD:

build() {
cd $srcdir/nut-$pkgver
./configure --with-user=nut \
--prefix=/usr \
--datadir=/usr/share/ups \
--sysconfdir=/etc/ups \
--with-group=nut \
--with-hal \
--with-usb \
--with-cgi \
--with-cgipath=/srv/http/cgi-bin/nut \
--with-htmlpath=/srv/http/nut \
--with-udev-dir=/etc/udev || return 1
<snip>

I'll see how this works

It works perfect when built with the options above:

http://www.3111skyline.com/download/screenshots/archlinux/network-ups-tools-rebuilt.jpg

Now it somebody could just make those the defaults, you wouldn't have to rebuild the package to get the web interface working. Let me know if you need anything else. Thanks.

a webapps should never write data on /srv

http://wiki.archlinux.org/index.php/Web_application_package_guidelines

lets try to improve it based on this guide

Hmm,

My bad on the issue of writing to srv. I modeled it on the openSuSE package which put the cgi files in /srv/www/cgi-bin/nut and the html files in /srv/www/htdocs/nut. Initially when I set up my Arch server I just moved my web apps from suse to Arch under /srv/www and the edited the httpd.conf file accordingly. I have since moved all web apps to /srv/http which seems to be the Arch standard. For web apps, especially with the tighter security required by php 5.3, it is difficult to install them anywhere without placing the web parts under the web server document root or needing to modify the apache config and add a new directory definition and then if php is required editing php.ini.

Arch defaults to /srv/http/cgi-bin for cgi files in its httpd.conf, see line 316:

316 ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"

so with the nut application needing to install both the cgi file and html files, the directory choices of /srv/http/cgi-bin/nut and /srv/http/nut, respectively, seemed appropriate. The files can go anywhere of course, so long as the web server can reach and use the files provided. Biru, what are your thought on how we can make it comply with the guidelines? Thanks.

I'm not sure what the solution to this will be, but with the new security restrictions in php 5.3, the proposed Web_application_package_guidelines do not seem to be workable without disabling the php protections that prevent following sym links or potentially exposing the entire /etc directory to php. The php settings that seem to cause the most grief with the guidelines are 'open_basedir' and 'include_path'. (note: for open_basedir, All symbolic links are resolved, so it's not possible to avoid this restriction with a symlink.)

I'll be happy with whatever decision of web app file placement is made by Arch, but it seems like not putting the cgi and web pages under /srv is a departure even from Arch's norm. The only other place for the cgi or web pages that strikes me as making sense is under /var like /var/srv/{cgi-bin/pkgname,htdocs/pkgname}. That way apache and php could be configured with /var/srv as a directory so config changes wouldn't be required with every web app installed. That would just mean changing the default httpd.conf and php.ini, but web apps will install OK.

Possibly installing to /usr/share/webapps/nut similarly to how phpmyadmin is handled?

that will be the case

OK Dan, the PKGBUILD with cgi & html going in /usr/share/webapps/nut. Hope it helps.