summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110118/002222.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110118/002222.html')
-rw-r--r--zarb-ml/mageia-dev/20110118/002222.html120
1 files changed, 120 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110118/002222.html b/zarb-ml/mageia-dev/20110118/002222.html
new file mode 100644
index 000000000..cfcf91c22
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110118/002222.html
@@ -0,0 +1,120 @@
+<!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=%3C201101181948.04290.maarten.vanraes%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="002221.html">
+ <LINK REL="Next" HREF="002223.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Proofreading web applications policy</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C201101181948.04290.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] Proofreading web applications policy">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Tue Jan 18 19:48:04 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy
+</A></li>
+ <LI>Next message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2222">[ date ]</a>
+ <a href="thread.html#2222">[ thread ]</a>
+ <a href="subject.html#2222">[ subject ]</a>
+ <a href="author.html#2222">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op dinsdag 18 januari 2011 19:07:00 schreef Remy CLOUARD:
+&gt;<i> Hello there,
+</I>&gt;<i>
+</I>&gt;<i> I started to have a look at the webapps policy.
+</I>&gt;<i>
+</I>&gt;<i> There&#8217;s something that has been bugging me for a while, that&#8217;s the
+</I>&gt;<i> apache-centric way of thinking of this policy.
+</I>&gt;<i>
+</I>&gt;<i> To me, there are valuable alternatives to apache that deserve to be
+</I>&gt;<i> treated equally.
+</I>&gt;<i> Here are the packages that provides webserver
+</I>&gt;<i>
+</I>&gt;<i> apache-ssl|apache-mpm-event|apache-mpm-peruser|nginx|lighttpd|
+</I>&gt;<i> cherokee|apache-mpm-itk|apache-mpm-worker|thttpd|apache-mpm-rsbac|
+</I>&gt;<i> apache-mpm-prefork|boa
+</I>&gt;<i>
+</I>&gt;<i> &#8220;These are the files that are susceptible to change during the
+</I>&gt;<i> application's lifetime. They go in /var/lib/foo. If they are supposed to
+</I>&gt;<i> be editable by the application directly from the web interface, they
+</I>&gt;<i> should be owned by apache user and apache group.&#8221;
+</I>&gt;<i>
+</I>&gt;<i> Could we create a generic group (webserver for instance) to allow
+</I>&gt;<i> webapps to play nice with these webserver ?
+</I>
+i think we could call it www-data so we can play nice in multidistro
+environment with idmapping (or possibly even no idmapping).
+
+&gt;<i> Same goes for logfiles and config files containing sensitive
+</I>&gt;<i> informations.
+</I>&gt;<i>
+</I>&gt;<i> I would also be in favor of creating subpackages for webapps that
+</I>&gt;<i> provides better integration with apache such as files in
+</I>&gt;<i> /etc/httpd/conf/webapps.d/.
+</I>
+i'm in favor of webapps that are webserver independant.
+
+&gt;<i> That way, webapps should have a Requires on webserver, and the
+</I>&gt;<i> subpackage should have one on apache.
+</I>&gt;<i>
+</I>&gt;<i> Another issue is the owner of /var/www. This directory is owned by
+</I>&gt;<i> apache-conf. Could we instead make a generic package called
+</I>&gt;<i> webserver-data for instance that would provide it ? This way each
+</I>&gt;<i> package providing webserver would have to require webserver-data.
+</I>
+www-data ? again?
+
+&gt;<i> Finally, that may be a little cosmetic detail, but I would prefer
+</I>&gt;<i> template files for apache to be in a separate file in SOURCES/ that&#8217;s
+</I>&gt;<i> included instead of creating it in the spec like:
+</I>&gt;<i> cat &gt; %{buildroot}%{_webappconfdir}/%{name}.conf &lt;&lt;EOF
+</I>
+agreed
+
+
+One more thing, for apache specific: apache has multiple layouts, and the
+current redhat-like one (or even mandriva-one) is not really that easy to
+configure. the debian-style layout with vhosting on by default is much easier
+imho. (perhaps vhosting by default could be something that all webservers are
+set up on.)
+
+However, this is all great, but we agreed to have mandriva-2010.2 upgrade
+paths. so don't forget about that.
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002221.html">[Mageia-dev] Proofreading web applications policy
+</A></li>
+ <LI>Next message: <A HREF="002223.html">[Mageia-dev] Importing RPM Spec File Syntax
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2222">[ date ]</a>
+ <a href="thread.html#2222">[ thread ]</a>
+ <a href="subject.html#2222">[ subject ]</a>
+ <a href="author.html#2222">[ 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>