<!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=%3C4F629F0C.9060603%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013133.html">
<LINK REL="Next" HREF="013156.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=%3C4F629F0C.9060603%40mageia.org%3E"
TITLE="[Mageia-dev] lighttpd and others now require apache">anssi at mageia.org
</A><BR>
<I>Fri Mar 16 03:01:48 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013133.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013156.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13145">[ date ]</a>
<a href="thread.html#13145">[ thread ]</a>
<a href="subject.html#13145">[ subject ]</a>
<a href="author.html#13145">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>15.03.2012 22:51, Guillaume Rousse kirjoitti:
><i> Le 08/03/2012 16:47, Guillaume Rousse a écrit :
</I>>><i> Le 08/03/2012 16:13, Pascal Terjan a écrit :
</I>>>><i> On Thu, Mar 8, 2012 at 14:57, Romain d'Alverny<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">rdalverny at gmail.com</A>>
</I>>>><i> wrote:
</I>>>>><i> On Thu, Mar 8, 2012 at 15:02, Guillaume
</I>>>>><i> Rousse<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">guillomovitch at gmail.com</A>> wrote:
</I>>>>>><i> Le 08/03/2012 14:38, Pascal Terjan a écrit :
</I>>>>>>><i> And for /var/www/html
</I>>>>>>><i> This should really be a server-neutral thing (with a better name for
</I>>>>>>><i> the user, like www-data) but I never took the time to do it :(
</I>>>>>><i>
</I>>>>>><i> What is needed exactly by various web servers ? I really doubt
</I>>>>>><i> anything else
</I>>>>>><i> as apache requires apache configuration file. And if it is just a
</I>>>>>><i> /var/www/html directory, there is no use to have a dependency for
</I>>>>>><i> something
</I>>>>>><i> any sysadmin is able to create himself.
</I>>>>><i>
</I>>>>><i> It helps when it works out of the box. A user may not be aware, at
</I>>>>><i> first, that a /var/www/html has to be created + an index.html file put
</I>>>>><i> in it, to see its Web server work. It's a good default behaviour
</I>>>>><i> confirming the install succeeded and that the server works, it saves a
</I>>>>><i> few seconds to everyone trying/doing it first.
</I>>>>><i>
</I>>>>><i> Now, maybe each web server package should check if this /var/www/html
</I>>>>><i> directory exists and create it if needed (or have /var/www/apache,
</I>>>>><i> /var/www/lighttpd, etc.)? Or should that be better handled by a
</I>>>>><i> separate unique package?
</I>>>><i>
</I>>>><i> I would prefer a package providing a web user and a default webroot.
</I>>>><i> Else we can have such shared user created in each of the packages...
</I>>>><i> It would be annoying to have to chown the writable directories when
</I>>>><i> switching between servers.
</I>>><i> Fine with me.
</I>><i> Well, some days ago I pushed a 'webserver-base' package, with the
</I>><i> following elements:
</I>><i> - /var/www and /var/www/html directories
</I>><i> - 'apache' user
</I>><i> - index.html page
</I>><i>
</I>><i> I've been curious, however, at the exact amount of shared elements our
</I>><i> various webservers packages currently use. And actually, only two
</I>><i> (apache and lighttpd) do share user and document root, the two others
</I>><i> (nginx and cherookee) being totally independant.
</I>><i>
</I>><i> In Fedora, they are all independant.
</I>><i>
</I>><i> So I'd rather revert the change, and make lighttpd autonomous also.
</I>><i> Unless someone can convince me there is an advantage having lighttpd
</I>><i> executing as 'apache' :)
</I>
The web applications policy has files being owned by 'apache' user, and
I don't see how that could work if lighttpd used a different user:
<A HREF="https://wiki.mageia.org/en/Web_applications_policy">https://wiki.mageia.org/en/Web_applications_policy</A>
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013133.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013156.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13145">[ date ]</a>
<a href="thread.html#13145">[ thread ]</a>
<a href="subject.html#13145">[ subject ]</a>
<a href="author.html#13145">[ 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>