Pretty soon we’ll be coming out of stealth mode … and in the meantime, I’m looking for a couple more clients.

I know most of the people who read this site are technically inclined, and quite a few of you have an interest in e-commerce. So, if you’d like expert guidance on building, managing, and growing a successful e-commerce site, and you’re interested in a sneak preview of what we’re bringing to market, lets talk.

Call me at (503) 701-4135, or send an e-mail to peat@peat.org. I look forward to hearing from you.

September 8, 2006

One of my clients has a firewall in front of his subversion server, which is accessed within the network with the svn+ssh method. However, outside of the network it’s a different story: the tunnel through the firewall puts the public SSH interface on a non-standard port … and svn+ssh doesn’t play well with non-standard ports.

What’s the work around? A one line tweak in your personal Subversion configuration file. I can only vouch for this on OS X, so your mileage may vary.

Load ~/.subversion/config into your favorite text editor.

Add one line to the [tunnels] section: altssh = /usr/bin/ssh -p alt_port

Then your access method to svn+altssh and you’re ready to rock:

svn checkout svn+altssh://me@host.com/path/to/repo

This raises an interesting question: what other non-standard methods are people using to access their repositories?

—

Update: Arlo Bendiken has a better solution to this particular problem in his comment below … put the alternate port into the SSH config, so that any SSH interaction with the host receives the correct settings. Thanks!