Web developer musings… and then some.

From the root directory of your repository, issue:

$ svn cp trunk/* branches/path/to/your/branch
$ svn cp trunk/.htaccess branches/path/to/your/branch
$ svn cp trunk/.*.sh branches/path/to/your/branch

Doing something like:

$ svn cp trunk/ branches/path/to/your/branch

Which is much easier to understand does not work as I expect; due to the extra “trunk/” suffix; i.e. “branches/path/to/your/branch/trunk”.

In case you’re migrating repository data anywhere:

svnadmin dump old_svn_repos --deltas > svnrepos.dmp
svnadmin create new_svn_repos
svnadmin load new_svn_repos < svnrepos.dmp

It’s done!

For web developers out there, imo it’s much easier to call ’svn update’ than to navigate the new admin interface (smooth as it may be).

See here for more instructions.

Let’s suppose I’ve designated my Subversion repository to be /home/svn/.

Now I want to create a project “wordpress”:

# svnadmin create /home/svn/wordpress

Assuming you use Apache, make sure that “wordpress” is owned by the Apache user; e.g. nobody.

# chown -R nobody:nobody /home/svn/wordpress

Now go to the “wordpress” directory that you wish to Subversion.

# cd /home/kzhiwei/wordpress/

Note that this is distinct from the Subversion project folder that was created previously. Then import:

# svn import . file:///home/svn/wordpress

You should get a whole bunch of messages listing the files that have been imported from /home/kzhiwei/wordpress/ into /home/svn/wordpress/.