blob: b3eed8b51b8edf3287193aaa630a724f3be5bdd4 (
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
|
<!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=%3C4F63F560.6080107%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013179.html">
<LINK REL="Next" HREF="013276.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=%3C4F63F560.6080107%40mageia.org%3E"
TITLE="[Mageia-dev] lighttpd and others now require apache">anssi at mageia.org
</A><BR>
<I>Sat Mar 17 03:22:24 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013179.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013276.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13185">[ date ]</a>
<a href="thread.html#13185">[ thread ]</a>
<a href="subject.html#13185">[ subject ]</a>
<a href="author.html#13185">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>16.03.2012 19:47, Juergen Harms kirjoitti:
><i> On 03/16/2012 01:00 PM, Malo wrote:
</I>>><i> It's better for now
</I>>><i> to say that web apps are packaged for apache, and maybe, in the wiki,
</I>>><i> people can
</I>>><i> write how to adapt to other web servers.
</I>><i>
</I>><i> Maybe the approach used for the backuppc package is a good compromise:
</I>><i> The package contains and installs the apache server definition. But the
</I>><i> package also contains a README.MGA file that - among other items -
</I>><i> contains a recommendation on how to create a backuppc server for lighttpd.
</I>><i>
</I>><i> This approach is perfectly in line with the "packaged-for-apache"
</I>><i> concept, and it makes life easy for users who - for whatever reason -
</I>><i> need to run lighttpd. The mageia wiki is great, and there is interest to
</I>><i> push people to go to the wiki. But a README file that comes with the
</I>><i> package is the first place where a user will look for this kind of
</I>><i> information; and it is more likely to get updated with a new release of
</I>><i> backuppc than a - separate - page in the wiki.
</I>
This doesn't work for webapps that need server-writable
directories/files that are owned by the server user, since any changes
to the ownerships the user makes would be overridden on upgrade.
Hence I suggest a single user id to be used. (I'm fine with any other
solution which works as well)
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013179.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI>Next message: <A HREF="013276.html">[Mageia-dev] lighttpd and others now require apache
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13185">[ date ]</a>
<a href="thread.html#13185">[ thread ]</a>
<a href="subject.html#13185">[ subject ]</a>
<a href="author.html#13185">[ 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>
|
