blob: 14c404213b67d51dd6c499ef9d3e50e2ee29f24e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proofreading web applications policy
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118180700.GA14361%40shikamaru.fr%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002316.html">
<LINK REL="Next" HREF="002222.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proofreading web applications policy</H1>
<B>Remy CLOUARD</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118180700.GA14361%40shikamaru.fr%3E"
TITLE="[Mageia-dev] Proofreading web applications policy">shikamaru at mandriva.org
</A><BR>
<I>Tue Jan 18 19:07:00 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete !
</A></li>
<LI>Next message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2221">[ date ]</a>
<a href="thread.html#2221">[ thread ]</a>
<a href="subject.html#2221">[ subject ]</a>
<a href="author.html#2221">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hello there,
I started to have a look at the webapps policy.
There’s something that has been bugging me for a while, that’s the
apache-centric way of thinking of this policy.
To me, there are valuable alternatives to apache that deserve to be
treated equally.
Here are the packages that provides webserver
apache-ssl|apache-mpm-event|apache-mpm-peruser|nginx|lighttpd|
cherokee|apache-mpm-itk|apache-mpm-worker|thttpd|apache-mpm-rsbac|
apache-mpm-prefork|boa
“These are the files that are susceptible to change during the
application's lifetime. They go in /var/lib/foo. If they are supposed to
be editable by the application directly from the web interface, they
should be owned by apache user and apache group.”
Could we create a generic group (webserver for instance) to allow
webapps to play nice with these webserver ?
Same goes for logfiles and config files containing sensitive
informations.
I would also be in favor of creating subpackages for webapps that
provides better integration with apache such as files in
/etc/httpd/conf/webapps.d/.
That way, webapps should have a Requires on webserver, and the
subpackage should have one on apache.
Another issue is the owner of /var/www. This directory is owned by
apache-conf. Could we instead make a generic package called
webserver-data for instance that would provide it ? This way each
package providing webserver would have to require webserver-data.
Finally, that may be a little cosmetic detail, but I would prefer
template files for apache to be in a separate file in SOURCES/ that’s
included instead of creating it in the spec like:
cat > %{buildroot}%{_webappconfdir}/%{name}.conf <<EOF
--
Rémy CLOUARD
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
URL: </pipermail/mageia-dev/attachments/20110118/d03ff77a/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002316.html">[Mageia-dev] GLUT (part of mesa srpm) is not GPL... and is quite obsolete !
</A></li>
<LI>Next message: <A HREF="002222.html">[Mageia-dev] Proofreading web applications policy
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2221">[ date ]</a>
<a href="thread.html#2221">[ thread ]</a>
<a href="subject.html#2221">[ subject ]</a>
<a href="author.html#2221">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
