Discussion:
Web App And The FHS
Charlie
2007-07-16 10:14:35 UTC
Permalink
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hello Web App mailing list<br>
<br>
I am a little confused,&nbsp; in section 3.1 of the Webapps Policy Manual<br>
it states:<br>
<br>
Static and dynamically interpreted content<br>
<br>
&nbsp;&nbsp;&nbsp; |/usr/share/PACKAGE/www|<br>
<br>
Dynamically executed content<br>
<br>
&nbsp;&nbsp;&nbsp; A unique subdirectory of either |/usr/lib/cgi-bin/PACKAGE| or<br>
&nbsp;&nbsp;&nbsp; |/usr/lib/PACKAGE| (architecture-dependant)<br>
<br>
&nbsp;&nbsp;&nbsp; or A unique subdirectory of |/usr/share/PACKAGE|<br>
&nbsp;&nbsp;&nbsp; (architecture-independant)<br>
<br>
A DD reviewed my package and suggested that I install into<br>
/usr/share/package/www and quoted this manual.<br>
<br>
The package I am working on is architecture-independent, so long as<br>
the webserver supports MySQL and PHP.<br>
<br>
Now the way I read this I should be installing into<br>
/usr/share/&lt;packagename&gt;.<br>
<br>
To help me get a better understand this, what is the difference<br>
between dynamically interpreted content and dynamically executed
content?<br>
<br>
Regards<br>
Charlie<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.6 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><br>
<br>
iD8DBQFGm0ULEzLCYCFq8VIRAi8XAJ46mwu2mq/gaXUcPtayK9p8wJeoeACgvQEw<br>
Yl9ANDgI4pBZcgSXgnnnaYw=<br>
=F+vp<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>
--
To UNSUBSCRIBE, email to debian-webapps-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
sean finney
2007-07-16 17:59:30 UTC
Permalink
hi charlie,
Post by Charlie
A DD reviewed my package and suggested that I install into
/usr/share/package/www and quoted this manual.
The package I am working on is architecture-independent, so long as
the webserver supports MySQL and PHP.
Now the way I read this I should be installing into
/usr/share/<packagename>.
i would say that this is correct. i usually recommend that you choose some
subdirectory of /usr/share/<package>, only because later you might need to
put other things from <package> in /usr/share that you don't necessarily want
as part of the website. so, in the webapps draft document, you see a
recommendation for /usr/share/<package>/www (though a /htdocs, /site, or
whatever would be just the same as far as i'm concerned).
Post by Charlie
To help me get a better understand this, what is the difference
between dynamically interpreted content and dynamically executed content?
yes, it's kind of vague... and is maybe even not so relevant any more.
honestly i think all references to packages using /usr/lib/cgi-bin should be
removed entirely... the main difference between the two is
that "interpreted" content are scripts that are opened, read, and interpreted
by the webserver itself, whereas "executed" are external (cgi) programs that
are run by the webserver. of course, it's possible that an application could
be both, as php supports both the standard mod_php style approach as well as
a fastcgi implementation.



sean

Loading...