server maintenance

[kaan]

At the end of february the server will be taken down permanently.
I will provide whoever that wants it with at full repository dump.

-klaus

[Ekmek]

Originally posted by BureauBert
Well actually I am running two CTP2-related websites , both of which are long-term projects in extremely slow progress and I would certainly be proud to host the source code project's version control system.

The CTP2 Bureau sits on a shared webspace (250 MB) which includes the usual combo PHP / Perl / MySQL, most Apache modules available (at least on friendly demand) -- that's it.

I have to admit that I don't know anything about Subversion but I am fairly sure it needs some special server software or rather: it is some special server software, which would go beyond the capacity of my humble webspace.

But if I am wrong and what the "CTP2 Bureau" can offer would be sufficient for Subversion (or some other appropriate solution) I would gladly agree on putting the project on this webspace (there are still plenty of MySQL-databases and subdomains available and most of the 250 MB is unused).
In this case I could provide some savvy and reliable team members with FTP-access and information needed to set things up and transfer the data. Since my spare time is *really* limited the aforementioned team members would need to take care of maintainance themselves.
Ah, yes -- bandwidth/traffic: it's unlimited but under the terms of fair use, whatever is done should not bog down the server and cause the hosting provider to fire me and my $!§*& websites

Anyway -- even if my webspace should be insufficient for setting up an appropriate version control system I can offer about 200+ MB just to save files and keep them accessible for the source code project team in case Kaan's server goes offline before a real alternative can be established.

Can anyone help BureauBert with this? If not I was thinking that if someone could set it up I think I have enough financial resources to keep it going, does anyone (kaan especially) know how much it will cost each month to have a SVN server running?

[ctplinuxfan]

Originally posted by E
Can anyone help BureauBert with this?

Unfortunately, BureauBert is right: subversion needs additional
software to be installed. On Ctp2 Bureau, no apache2 is running,
so there would would only be two possible setups:[list=1][*]subversion as a standalone server (listening on a dedicated port
like on kaan's server)[*]parallel apache 2 installation listening on a different port with
mod_dav and mod_svn[/list=1]

On the other site, a customized apache is running (most probably no
apache2, either). If it was apache2, mod_dav and mod_svn have to
be installed, too. If not previous setups apply.

For more details, see 6. Server Configuration.

In each case, you would require access to the server for ACL-Setup
(i.e. updating usernames and their passwords either within
svnserve.conf and passwordfile (1rst case) or .htpasswd (2nd
case)). E.g. these could be uploaded into a restricted directory and
copied/chowned over subversions configurations via a daily cronjob.

Although the chances are small they'd install it without any
additional costs, it's worth a try to ask when we know the previous
traffic.

If not I was thinking that if someone could set it up I think I have enough financial resources to keep it going, does anyone (kaan especially) know how much it will cost each month to have a SVN server running?

Well, don't forget that much traffic can be avoided by reloading a
complete repository dump and telling each one to use

svn switch --relocate

If this was too expensive, we could also provide a repository dump
and start an altered "Altered source files" thread, each coder has a
local repository kept in sync with all other repositorys. Each commit
consists of two replies to that thread like this:
[list=1][*]First reply: Contents current revision and "lock", e.g. "999 lock".
As soon, as the reply is submitted and there is no other lock reply,
you can start the commit locally and create an incremental dump of
the last revision (named .diff because .dump is not supported, e.g.:
1000.diff).[*]Second reply: Contains the log message and the revision dump
as an attachment/Link to uploaded file. As soon as this reply is
submitted, anybody else can proceed with downloading revision
1000, loading it into the repository, mergin, locking 1000 and
committing 1001 like before.[/list=1]
If at any time we get two locks simultanously, only the poster of first
"lock" reply may start a commit, the others have to try locking again
after the commit and dump have been submitted.

Last but not least, perhaps somebody else can host the server.