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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B810%5D%20split%20subversion-tools%20in%20its%20own%20class%2C%0A%20to%20prepare%20for%20svn%20mirror&In-Reply-To=%3C20110116194131.GA26385%40sisay.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002141.html">
<LINK REL="Next" HREF="002143.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror</H1>
<B>Michael scherer</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B810%5D%20split%20subversion-tools%20in%20its%20own%20class%2C%0A%20to%20prepare%20for%20svn%20mirror&In-Reply-To=%3C20110116194131.GA26385%40sisay.ephaone.org%3E"
TITLE="[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror">misc at zarb.org
</A><BR>
<I>Sun Jan 16 20:41:31 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002141.html">[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror
</A></li>
<LI>Next message: <A HREF="002143.html">[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2145">[ date ]</a>
<a href="thread.html#2145">[ thread ]</a>
<a href="subject.html#2145">[ subject ]</a>
<a href="author.html#2145">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sun, Jan 16, 2011 at 02:49:41PM +0100, nicolas vigier wrote:
><i> On Sun, 16 Jan 2011, Michael scherer wrote:
</I>><i>
</I>><i> > On Sun, Jan 16, 2011 at 02:15:35PM +0100, <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">root at mageia.org</A> wrote:
</I>><i> > > Revision: 810
</I>><i> > > Author: misc
</I>><i> > > Date: 2011-01-16 14:15:35 +0100 (Sun, 16 Jan 2011)
</I>><i> > > Log Message:
</I>><i> > > -----------
</I>><i> > > split subversion-tools in its own class, to prepare for svn mirror
</I>><i> > >
</I>><i> >
</I>><i> > Since we still do not have any svn viewer system, I had a idea that
</I>><i> > would allow us to have one without sacrifiying security :
</I>><i> > - use a viewer with a readonly clone of svn.
</I>><i> >
</I>><i> > For example, we could use svnsync on alamut to copy the svn from valstar.
</I>><i> > ( I tried svm, but it seems to be quite broken ). I have a module ready to
</I>><i> > be committed for that.
</I>><i> >
</I>><i> > This way :
</I>><i> > - we have backups ( until someone do a full real backup system, and
</I>><i> > so until we have fiona )
</I>><i> > - someone compromissing the server cannot modify the svn ( as this is a copy )
</I>><i> > - we will have local access to the data
</I>><i> > - full range of web interface ( and not just viewvc, even if I think it is fine )
</I>><i> > - local access is faster than remote ( after testing viewvc )
</I>><i> > - the svn server will not be loaded with web request while at the same time
</I>><i> >
</I>><i> > The only issue is the bin-repos svn repository. I am not sure that it would be wise to
</I>><i> > mirror it on alamut. But we can decide to at least offer viewvc for adm, packages, and web ?
</I>><i>
</I>><i> Yes, it looks like a good idea.
</I>><i> Only issue would be that we can't see the latest commits immediately.
</I>><i> But if we mirror often, it should be ok.
</I>
Depend if the sync is push or pull.
Ie, we can use ssh::auth to generate keys to push and run a snvmirror sync on commit.
For the moment, I have done it with cron ( safer from my pov ), but we can change
later if needed.
><i> Now we need to find a vhost name for the web interface ? svnweb.mageia.org ?
</I>
That seems a call for bikeshedding :p
Shouldn't we first decide the software to use ?
So far there is ( on top of my head ) :
- viewvc
- websvn
Viewvc do requires a patch to handle big repositories, was what we used
at mdv. It requires mysql db for searching the repository ( but
we can disable it, or port to postgresql if we have time ), and a
backport for fastcgi support.
I didn't look much at Websvn, except that it requires to run svn on the
commandline. While this sound like bad idea for
performance reasons, it is also a php web application, so this could
conflict with sushosin, or similar protection system. I do not
know how it handle big repositories, nor the exact requirements except
"php".
Anyone who want to work and compare both in term of useful
features ?
( I would favor viewvc, but I am biased toward my tutelar language. )
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002141.html">[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror
</A></li>
<LI>Next message: <A HREF="002143.html">[Mageia-sysadm] [810] split subversion-tools in its own class, to prepare for svn mirror
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2145">[ date ]</a>
<a href="thread.html#2145">[ thread ]</a>
<a href="subject.html#2145">[ subject ]</a>
<a href="author.html#2145">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
