Moving SVN to the new server
Posted: Thu Apr 03, 2014 5:12 pm
Hey,
I'm planning the move of the SVN repository to the new
server at orxonox2.vseth.ethz.ch. I plan on keeping this thread up to date with
what I find out and plan to do so you guys can give me feedback. This first
post is just a list of what I've found out so far:
libapache-svn, then rsyncing the /var/svn/game folder as well as the svnusers,
svnaccess and svnaccess-read-only files to the new server's /var/svn and
see whether I can check out and commit with my user.
Before we do the full transition, I'll be looking at redirects. Beni and I already
talked a bit about them, apparently they are currently simply done as apache sites.
This will likely mess up the certificate stuff even further, but that's a separate issue.
But in theory, if redirects work well, we can do the change from the old to the new
server without users noticing anything or having to re-checkout their repos - similar
to what Beni has done with the forum.
What do you guys think? Are my assumptions correct? I also wanted to ask here
before I go around installing stuff on the new server.
I'm planning the move of the SVN repository to the new
server at orxonox2.vseth.ethz.ch. I plan on keeping this thread up to date with
what I find out and plan to do so you guys can give me feedback. This first
post is just a list of what I've found out so far:
- The SVN repository we're currently using is stored on the old
server in /var/svn/game/ and is about 3.3 gb in size. - This folder can just be copied to a different place using tools like
rsync. I tried that today with copying it to my home computer and I could
check out the trunk and data_extern locally without any issues. - The SVN access from externally seems to be handled using libapache-svn
and the apache site 02_svn.orxonox.net.conf. This also specifies to use
the /var/svn/svnaccess-read-only file for authorization purposes.
libapache-svn, then rsyncing the /var/svn/game folder as well as the svnusers,
svnaccess and svnaccess-read-only files to the new server's /var/svn and
see whether I can check out and commit with my user.
Before we do the full transition, I'll be looking at redirects. Beni and I already
talked a bit about them, apparently they are currently simply done as apache sites.
This will likely mess up the certificate stuff even further, but that's a separate issue.
But in theory, if redirects work well, we can do the change from the old to the new
server without users noticing anything or having to re-checkout their repos - similar
to what Beni has done with the forum.
What do you guys think? Are my assumptions correct? I also wanted to ask here
before I go around installing stuff on the new server.