summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-March/013167.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-March/013167.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/013167.html')
-rw-r--r--zarb-ml/mageia-dev/2012-March/013167.html96
1 files changed, 96 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/013167.html b/zarb-ml/mageia-dev/2012-March/013167.html
new file mode 100644
index 000000000..20b1aa3d9
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-March/013167.html
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] lighttpd and others now require apache
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F634026.7060201%40mageia.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="013659.html">
+ <LINK REL="Next" HREF="012835.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] lighttpd and others now require apache</H1>
+ <B>Anssi Hannula</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20lighttpd%20and%20others%20now%20require%20apache&In-Reply-To=%3C4F634026.7060201%40mageia.org%3E"
+ TITLE="[Mageia-dev] lighttpd and others now require apache">anssi at mageia.org
+ </A><BR>
+ <I>Fri Mar 16 14:29:10 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="013659.html">[Mageia-dev] lighttpd and others now require apache
+</A></li>
+ <LI>Next message: <A HREF="012835.html">[Mageia-dev] lighttpd and others now require apache
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#13167">[ date ]</a>
+ <a href="thread.html#13167">[ thread ]</a>
+ <a href="subject.html#13167">[ subject ]</a>
+ <a href="author.html#13167">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>16.03.2012 11:02, Guillaume Rousse kirjoitti:
+&gt;<i> Le 16/03/2012 03:01, Anssi Hannula a &#233;crit :
+</I>&gt;&gt;&gt;<i> So I'd rather revert the change, and make lighttpd autonomous also.
+</I>&gt;&gt;&gt;<i> Unless someone can convince me there is an advantage having lighttpd
+</I>&gt;&gt;&gt;<i> executing as 'apache' :)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> The web applications policy has files being owned by 'apache' user, and
+</I>&gt;&gt;<i> I don't see how that could work if lighttpd used a different user:
+</I>&gt;&gt;<i> <A HREF="https://wiki.mageia.org/en/Web_applications_policy">https://wiki.mageia.org/en/Web_applications_policy</A>
+</I>&gt;<i> This policy was crafted with apache in mind only, not all available web
+</I>&gt;<i> servers. And its explicitely refers to apache integration, not generic
+</I>&gt;<i> webserver compatibility. For instance, the configuration file provided
+</I>&gt;<i> is apache-specific. Even if we have compatible file permissions, and if
+</I>&gt;<i> we asked packagers to also provide a default lighttpd configuration file
+</I>&gt;<i> (slighly more work), that would still be mostly theorical compatibility
+</I>&gt;<i> without actual testing from the packagers (many more work).
+</I>&gt;<i>
+</I>&gt;<i> So, rather than a potential compatibility, without documented limits,
+</I>&gt;<i> should we rather not make clear than adapting our web applications
+</I>&gt;<i> package to any other web server than apache is fully up to the end user ?
+</I>
+It is rather easy for the user to create a lighttpd configuration file
+themselves etc, however it is much more difficult for the user to start
+changing/guessing the needed file permissions for the larger applications.
+
+Also, any changes would be overwritten by any upgrade, which is quite
+bad IMO.
+
+(and yes, I do have seen actual users using lighttpd with our webapp
+packages)
+
+--
+Anssi Hannula
+</PRE>
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="013659.html">[Mageia-dev] lighttpd and others now require apache
+</A></li>
+ <LI>Next message: <A HREF="012835.html">[Mageia-dev] lighttpd and others now require apache
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#13167">[ date ]</a>
+ <a href="thread.html#13167">[ thread ]</a>
+ <a href="subject.html#13167">[ subject ]</a>
+ <a href="author.html#13167">[ 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>