On Wed, Sep 2, 2009 at 08:47, el_es<el.es.cr_at_gmail.com> wrote:
> I am about to migrate the repository of SVN, created with Tortoise, to a
> Linux-based server (running Ubuntu Intrepid).
> Which method is better (after setting server access and paths that is) :
> 1) copy the repository files from the Windows machine to where I want to have
> them served (it is the native FS it's created on the current host) on the Linux
> 2) set up server access in Tortoise and use it to import project(s) to the Linux
> server ?
Neither. Install the command-line Subversion on the Windows machine.
Dump the repository, move the dumpfile to the Linux box, run svnadmin
create to create a new, empty repository, then run svnadmin load to
import the repository history. See
> The repository so far only hosts projects written by one man (me and my
> predecessor, but not at the same time) and now I need to set it up so another
> man can access it, preferably preserving the history - so the import is probably
> preferred? If the copy method could work, I'd probably need to run svn files via
> dos2unix (for cr-lf conversion) ? (the project(s) files however, are supposed to
> be Windows only)
Your line endings should be managed by setting the svn:eol-style
property appropriately on your files.
> After the migration, I will only use server connection (will not use the local
> repository any more)
> Btw, which method of access is :
> -faster at local network level (comparable to samba file transfer) (I gather,
In descending order of speed:
file:/// (but this should never be used over a network or with more than 1 user)
svn+ssh:// (I may be wrong on the position of this one)
> - secure at the outside access (Webdav over https?)
> at the same time ?
https or svn+ssh
> - easier to set up than svn:+ssl (WebDAV+https?)
svn+ssh is the trickiest to setup IMHO. https is probably the best mix
of security & simplicity.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-02 15:13:05 CEST