September 27, 2006
This is an exciting year: My company is growing, our prototypes are working exactly as we hoped, and we’ll be rolling out our first public products and services over the next few months.
What’s really exciting is watching our clients succeed: they’re doing phenomenally well. In one case, they’ve seen monthly revenue grow over 2000% — in 2007, they’ll easily clear a million dollars in sales.
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 email@example.com. I look forward to hearing from you.
September 8, 2006
Looks like the Washington Post has a writeup of my aunt Kit‘s book about Louisa May Alcott, which should be hitting the shelves on September 12th. Good stuff! The Wife is in Boston for the official book launch and a couple of Red Sox games — I have to say I’m a little jealous.
So, if you’re in or near Concord, Massachusetts, and you’re keen on a rather interesting discussion about Miss Alcott, check out the official launch event:
Tuesday, September 12, 2006, 7:30 pm
Orchard House – Home of the Alcotts
399 Lexington Road
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.
~/.subversion/configinto your favorite text editor.
- Add one line to the
altssh = /usr/bin/ssh -p alt_port
Then your access method to
svn+altssh and you’re ready to rock:
svn checkout svn+altssh://firstname.lastname@example.org/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!