How to set this up in uberSVN

RustedBucket
RustedBucket
Ok, so I'm having a bit of a brain fart here. What I want to do seems pretty simple. We currently have our svn located at:  https://dev.domain.com/svn/    This works great, except I've been looking at uberSVN for the GUI admin. In moving to the new server what I want to do is setup the svn like this:  /opt/ubersvn/repositories/repos/  /opt/ubersvn/repositories/archives/    Mostly because we have lots of old stuff to keep and the devs want to separate it from the new stuff we are doing.... whatever right.....    So what I want is an svn target like this: https://svn.domain.com/repos/ or https://svn.domain.com/archive/    The only way I can figure this when creating the repository in the uberSVN GUI is by specifying the target in the location like this:    REpo Name: Project1  Location: repos/project1    Is this right or is there another way?

Last updated

Leon
Leon
I think I'm having a similar problem. I'm migrating from VisualSVN server to UberSVN. My users are fond of externals in their repositories and this is presenting a challenge in the migration process.    Old URL: https://server/svn/  New URL: https://server/    This will break the externals in all of my projects that use the old url structure unless I can make the new URL match.    Any help would be appreciated!  Leon
RustedBucket
RustedBucket
Yeah, I've beat on this for a couple of days but I think the conclusion I've come to is to add the sub-dir to the project path when creating the repository. (ie: svn/). On disk this creates a sub-dir and then the repo-dir, seems to work, just kind of a pain. I think uberSVN should add a setting for SVNParentPath at the repo level, instead of SVNPath.
RustedBucket
RustedBucket
Leon, something else I discovered you might try. If the externals are dependent on physical disc location then I think the way I suggested will have to be used, but you can also go into the repository administration and change the Location after it's created. So if your physical location is something like repositories/ changing the location here to svn/project will change the apache location directive but not the physical path like it does if you set it on repo creation. You end up with this: http://domain.com/svn/project => /opt/ubersvn/repositories/project  I think this is confusing in the interface now, hopefully they'll clean that up in the future.

1-4 of 4

Reply to this discussion

You cannot edit posts or make replies: You should be logged in before you can post.