CODEBOXER.com

this worked for me

1 May 2009 | 11:56 am by codeboxer

recursevly remove .svn files from an existing repo.

If you need to take a project out of scm, you can run this bash script from the top folder - and it will remove all .svn folders recursively.

Works well for
- changing an svn checkout into and svn export
- switching from svn to git

find . -type d -name '.svn' -exec rm -rf {} \;

git ftw

19 February 2009 | 3:00 pm by codeboxer

copied from:
Cleanly Migrate Your Subversion Repository To a GIT Repository

The first thing we need to do is create a users file that maps all your SVN users to your GIT users. Just make a file on your Desktop named 'users.txt'. Map the users using this format:

jmaddox = Jon Maddox
bigpappa = Brian Biggs

Simple. Now here are the commands you'll run. I'll explain them below.

mkdir my_blog_tmp
cd my_blog_tmp
git-svn init http://code.yoursite.net/my_blog/trunk/ --no-metadata
git config svn.authorsfile ~/Desktop/users.txt
git-svn fetch

The first two are self explanatory, we're making a new directory for the temporary repository. The second command initializes the directory as a git-svn hybrid thing and points the origin at your SVN repository. The flag, --no-metadata, tells GIT to leave all the SVN details behind (not the commit log). The fourth command tells GIT to remap all the SVN users to GIT users when it sucks down the source and history. The last command actually does the fetching.

Ok, so now after a few LONG minutes, your source is all there. Do a git log to see that your users have been mapped. Sweet!

Now you just have one last step. You need to clone this repository. Why do we do this? When doing a normal git clone it will take everything we want from the temporary repository, while leaving behind all the SVN cruft that was there to support the git-svn stuff.

git clone my_blog_tmp my_blog

Original post blogged on codeboxer.com.

DREAMHOST Worst host evar

3 December 2008 | 3:24 am by codeboxer

Dreamhost is also pretty crappy, if you need Ruby on Rails support. Why does everyone advertise RoR and then not support it?

It looks like a decent Hostmonster style host, with a snazzy interface, but at the end of it here were the problems:

Terrible SVN support; let me say that again - SVN kind of sucks already, but I ended up with a bunch of 500 errors, and I don't need anyone to help SVN suck more than it already does.

SOME good wiki stuff, but it was out of date, was NOT supported (see above), so I got frustratingly 80% close to a real capistrano deploy and then could not finish because were server compatibility issues (an old Ruby version) and without direct shell access I was fecocked. Then my SVN got corrupted. Fun!

With Dreamhost, if you aren't paying for a hosting service, you can't even manage your domain forwarding.

So I am still on the lookout for a good Ruby host and I am not any closer.

As a recap - DREAMHOST is the worst Ruby on Rails hosting service EVER! They are, of course, right there next to Joyent, who also has a large home in Crapistan.