SSH Control News

Monday, December 15, 2008

SSH Control maintenance success

We apologize for any inconvenience if you tried to access your repositories today. Good news is the needed maintenance was a success and we are looking forward to uninterrupted service for the months ahead.

Friday, December 12, 2008

SSH Control down for maintenance Dec 14

Between 12pm - 8pm PST, SSH Control services will be suspended to do maintenance on our servers. We apologize for the inconvenience.

Friday, May 16, 2008

New project creation form

SSH Control improved Javascript Create Project form according to user feedback.

Monday, May 12, 2008

Source Code Haven

reprinted from

Rudi and I easily keep at least a few dozen software projects between us, and have hosted a few Subversion source code repositories for clients. Anyone who’s tried to setup a private revision control system, with secure SSH access and to be used among more than a few developers, knows that it can be a pain in the butt. Each SSH key has to be manually setup in a such a way to ensure developers can’t compromise the server. Developers forget the URIs to their repositories or have to resend you new keys because they’ve misplaced their private keys. Sometimes you just want to give developers read-only access, but dealing with permissions is such a hassle that tar-ing up your code and posting it on a website is much more convenient—even though it will eventually get stale and you would have to manually tar-up your code again.

Then there is the developer’s point of view. Rudi and I have hosted our open-source repositories at Sourceforge and Berlios, both popular CVS and Subversion services, but the very act of starting a repository took days because projects had to be pre-approved and you had to figure out how to install your SSH keys yourself which was often frustrating.

Rudi and I also had the problem of hosting way too many private repositories without any sort of system to track them — forgotten usernames, forgotten URIs. Frankly, I know the source code for this blog is in a revision control system somewhere, but we’ve bounced our repositories from one server to another, as well as converted from Subversion to Mercurial, that I can’t honestly tell you where the repository is, or under what system it’s under.

Hopefully with SSH Control, I can finally get organized. Rudi and I created SSH Control for all the reasons stated above, and it’s a really sweet system. Setting up a repository takes a minute. Inviting other developers is trivial. Installing SSH keys is a matter of just copying and pasting the key into a web form for your project. And we can upload old repositories, and, here’s the kicker, convert old repositories to another repository type while keeping all the changeset history.

We’ve still got some work to do, particularly with some of the displays, but we’ve been using the system for a month so far, and it works great for us. We have just opened SSH Control to the public last night. No new registrations yet, but I imagine that anyone looking to start a Subversion, Mercurial, or Git repository with SSH access will have an easy time at SSH Control.

Sunday, May 11, 2008

SSH Control opens public registration

Registration now available to the public. We encourage all developers who care about their code to signup! Create a free git, mercurial or subversion project, upload an existing repository, or convert your old one.