Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SVN issue with accessing old repository in new machine

 
Varshini Priya
Ranch Hand
Posts: 95
Eclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

We have an issue in setting up the svn. Our svn machine got crashed and we have got the backup of our svn. We have a new machine now and installed svn server. I would like to know how to go about in integerating my old svn contents with the new one. In the new machine, I have set up the svn server and have created a sample repository to test the same. It seems to be working fine. I have copied the old repository data to the new machine and once i start the svn server, Im able to view the contents of the old svn as well. However, I would require help in the following things

1. How to integerate the old svn contents with the new one.I tried to copy the contents of the old svn to the svn repository, but im unable to view the contents of the same.
2. I would like to know how to create the url for others to access from other machine. The old svn repository has got certain user permission set up and I would like to know how to setup/integerate the same in the new svn.

We are using Collabnet subversion server(1.8 in the new m/c. the older m/c had was running on collabnet server 1.5) and tortoise svn client to view the contents of the server. This is installed in a windows machine.

Any help on this is much appreciated. Thanks
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18009
47
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Subversion is built on the concept of a plug-in database for the repository, and if your old subversion was really old, you may want/need to convert it to the newer storage format. The Red Bean book should tell you how.

Probably the most common way to share a subversion repository is to install the Apache web server plus the mod_dav and mod_svn Apache modules. That will allow you to access the repository via HTTP. Security is supplied via the common Apache security services (such as .htaccess).

You can also run a stand-alone svn server the way CVS servers used to be run, with its own network listening port, but that's less flexible. I don't bother.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic