Holger Levsen wrote:
> Hi Tom,
>
> (it would be nice not to cc: me when mailing the BTS, I'm subscribed to the
> munin package :-)
>
> On Sonntag, 27. September 2009, Tom Feiner wrote:
>> I think the webapps policy outlines the right thing to do in this case,
>> however it focuses on what needs to be done for new packages, and its not
>> clear how the migration should be handled in upgrades, I guess that's where
>> debian-devel can help.
>>
>> http://webapps-common.alioth.debian.org/draft/html/
>
> I dont see it in there. Can you help me please? Neither 3.1 nor 5.1.1 is
> helpful AFAICS...
Well, 3.1 points to the correct location for the static/interpreted files, and
also mentions where not to put content:
From 3.1:
--------
Web applications should follow the same guidelines as any other software. Most
specifically, they should not make any assumption about how the administrator
has arranged the file hierarchy outside of the FHS by placing files in
non-standard places such as /home, /srv, /var/www or /usr/local.
Specifically, the following table should serve as a guideline for the
placement of files:
Static and dynamically interpreted content
/usr/share/PACKAGE/www
Dynamically executed content
A unique subdirectory of either /usr/lib/cgi-bin/PACKAGE or
/usr/lib/PACKAGE (architecture-dependant)
or A unique subdirectory of /usr/share/PACKAGE (architecture-independant)
--------
This is exactly how other packages, like phpmyadmin work (they too needed to
migrate from /var/www to /usr/share/PACKAGE/).
So it looks like /usr/share/munin/www is the right place for the static stuff
(logo, css, ext).
Regarding the graphs generated by munin-graph, and placed in /var/www/munin
(today), I agree there's no indication in the document on where to place these
files, I guess that's where we need advice from debian-devel.
Regards,
Tom Feiner
Attachment:
signature.asc
Description: OpenPGP digital signature