On Tue, Jun 28, 2005 at 03:38:08PM +1000, Kai Hendry wrote: > On Tue, Jun 28, 2005 at 01:07:25AM -0400, sean finney wrote: > > say you have a php app that has some php include libraries and some > > other stuff, you might want to have them seperated out like: > > > > /usr/share/foo/www <- web documents > > /usr/share/foo/include <- php include files > > PHP includes usually sit in the www accessible directory. This might be > confusing. > They shouldn't, it's a security risk to have these things publically accessable. Things which don't HAVE to be in the doc root, shoudn't be. See http://lists.debian.org/debian-security/2005/04/msg00103.html > > /usr/share/foo/scripts <- other helper scripts that don't belong in /usr/bin > > Do you have an example? I keep "dodgy" scripts in > /usr/share/doc/foo/example > /usr/share/foo/scripts shouldn't be used for 'dodgy' scripts. You're right to place them in /usr/share/doc/foo/example However, somthing that performs maintainace (for example) could live in /usr/share/foo/scripts > > /usr/share/foo/data <- other non web data, like xml or text files > > A data store off /usr/share/foo/ ? Sounds strange. > Yup, but that's because we're used to using /usr/share/foo/. We're trying to split up /usr/share/foo/ into sub directrories to make everything more sane. > And should the Debian package maintain it directly? > I'm not really sure what you mean here. For info, the (normally) latest release of the WebApps policy can be found at http://people.debian.org/~neilm/webapps-policy/ Regards, Neil McGovern -- __ .Ž `. neilm@debian.org : :' ! ---------------- `. `Ž gpg: B345BDD3 `- Please don't cc, I'm subscribed to the list
Attachment:
signature.asc
Description: Digital signature