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
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-webteam] [Mageia-sysadm] Wiki setup
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20%5BMageia-sysadm%5D%20Wiki%20setup&In-Reply-To=%3C1294618023.30856.41.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000121.html">
<LINK REL="Next" HREF="000124.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-webteam] [Mageia-sysadm] Wiki setup</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20%5BMageia-sysadm%5D%20Wiki%20setup&In-Reply-To=%3C1294618023.30856.41.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-webteam] [Mageia-sysadm] Wiki setup">misc at zarb.org
</A><BR>
<I>Mon Jan 10 01:07:03 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="000121.html">[Mageia-webteam] [Mageia-sysadm] Wiki setup
</A></li>
<LI>Next message: <A HREF="000124.html">[Mageia-webteam] Mailling lists for web team
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#122">[ date ]</a>
<a href="thread.html#122">[ thread ]</a>
<a href="subject.html#122">[ subject ]</a>
<a href="author.html#122">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le lundi 10 janvier 2011 à 00:24 +0100, Romain d'Alverny a écrit :
><i> On Mon, Jan 10, 2011 at 00:04, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">misc at zarb.org</A>> wrote:
</I>><i> > And the downside is that you will have one and only one server for wiki,
</I>><i> > no way to split among many server ( as noted by Benoit Audouard ).
</I>><i>
</I>><i> There would be ways to do so, if needed (front prox[y|ies] with
</I>><i> rewrite/redirection rules to name one).
</I>><i>
</I>><i> The question is, do we need to plan today for this kind of scaling issue?
</I>
I do not think, but on the other hand, it may much easier now that
later. And well, even if there is lots of ram on alamut, I wonder what
would happen if we do have a crash ( ie, would we be able to cope with
the load spread on other server in case of crash ).
We do not intend to have a crash, and so far, i think we would be mostly
safe ( once we do have a backup server ), but it is not to me to remind
the fate of Mandriva servers :/
><i> > Now, what I would want to see is :
</I>><i> > 1) who decide the language that goes ( because someone has to decide, I
</I>><i> > do not think that media is so flexible that anybody can start here own
</I>><i> > language, and if there
</I>><i>
</I>><i> That would be a wiki team (that is a mix of i18n and doc team I
</I>><i> guess?). Against a specific policy (like, having a sufficient list of
</I>><i> involved-enough people to take care of a newly open wiki locale).
</I>
Yup, so that should be decided ( not right now, but taken care if
possible before announcing the wiki ).
Just also to be sure, we do not plan for any specific complex acl ?
( IMHO, we should try to avoid, and if not possible, use group acl if
possible, and in last ressort, login based acl to avoid duplication ).
><i> > 2) How many database do we need ( ie, creation of 1 big db, or several
</I>><i> > smaller one ).
</I>><i>
</I>><i> 1 per language.
</I>
Good.
Can I also remind that we try to use postgresql everywhere, and that
would be nice to keep it this way ( mediawiki does support it, so that's
just to remind when doing the test ) ?
><i> > 3) is this : 1 big wiki instance, or several smaller one ?
</I>><i>
</I>><i> Depends how you set it up. @ Mandriva, we had a single code instance,
</I>><i> and small custom config files (1 per locale).
</I>
I would favor this too because that's seems simpler.
><i> > Do we ever plan to have wiki not linked to language content ? ( like per
</I>><i> > team wiki, or that will be section on the english one ? )
</I>><i>
</I>><i> I did not understand this one. :)
</I>
Ie, there will be only wiki/en, wiki/de, wiki/pt ?
No wiki/team/sysadmin/ , or something like that, or per project wiki if
any ?
><i> > I guess I can also take for granted that we will not manage 1 set of
</I>><i> > extension per language ?
</I>><i>
</I>><i> Same codebase for every locale if possible (that's achievable).
</I>
Good, so that mean that there is only 1 wiki team, and not several one
( like it was at Mandriva (or at least, like i thought it was)).
I assume that this will be handled like i18n ?
Otherwise, each team will want a different set of extensions ( or at
least, the risk is not null that 2 teams request 2 redundant or
incompatible extensions, based on personal preference ).
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000121.html">[Mageia-webteam] [Mageia-sysadm] Wiki setup
</A></li>
<LI>Next message: <A HREF="000124.html">[Mageia-webteam] Mailling lists for web team
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#122">[ date ]</a>
<a href="thread.html#122">[ thread ]</a>
<a href="subject.html#122">[ subject ]</a>
<a href="author.html#122">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam
mailing list</a><br>
</body></html>
|
