ChiliProject is not maintained anymore.
Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and
we urge all existing users to migrate their data to a maintained
system, e.g. Redmine. We will
provide a migration script later. In the meantime, you can use the
instructions by
Christian Daehn.
Forums » Discuss »
Import project from a stand-alone SVN server?
Added by Björn Blissing at 2012-04-04 07:39 am
I have my ChiliProject 3.0 server up and running with a couple of projects active. But now I need to import an project that has been running on a stand-alone SVN server. What is the best procedure to migrate from the stand-alone server?
I would like to retain the old history and be able to link the old usernames on the SVN server to the correct usernames at the Chiliproject server.
I guess the first step is to dump the SVN database from the old server with SVNADMIN DUMP
. But what would my next steps be?
If you only want read access to the svn repositories you can do it over http, no need to migrate the repositories there.
Well, I do need more than read access. My goal is to do a complete migration of the repository, to be able to retire old server. Also I would like to be able to use the some of the features available with Chiliproject, i.e. user access control.
Ideas? Anyone?
Well doing a simple migration from one SVN server to another is one thing (and I have done it before). But how do I get Chiliproject to pickup the meta-data, i.e. user names?
Could the procedure be as simple as this:
- Dump database with
SVNADMIN DUMP
from old server.
- Use
SVNDUMPFILTER
to rename old user names to user names used on my ChiliProject Server.
- Create new project on my Chiliproject server (and let reposman.rb script create a new svn repository as normal).
- Load the filtered SVN Dumpfile into my newly created repository with
SVNADMIN LOAD
.
- Done???
Well, I've never migrated an svn repository while also changing the usernames in the history, but if it's possible, yes, do it :-) If you don't want to touch the history, ChiliPoject also has a per-project settings page where you can match svn usernames it couldn't find in ChiliProject to ChiliProject users.
All in all, your procedure looks sound, note that you will need to install the perl module into the apache serving your svn repositories as well if you want to use the ChiliProject users and project memberships as authentication and authorization source.