Daikini

I’ve renewed the svn.roundhaus.com SSL certificate today which means that the subversion client may prompt with an “Error validating server certificate message”.

This is correct and the proper solution is to either accept (t)emporarily, which means the subversion client will prompt again next time it connects to svn.roundhaus.com, or to accept (p)ermanently, which means that the subversion client will not prompt again with this message until next year when the certificate is renewed again.

If this isn’t clear or there are any questions please email support at roundhaus.com.

Error validating server certificate for 'https://svn.roundhaus.com:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: svn.roundhaus.com
 - Valid: from Sat, 19 Apr 2008 23:09:14 GMT until Wed, 20 May 2009 23:09:14 GMT
 - Issuer: Equifax Secure Inc., US
 - Fingerprint: 59:39:e8:5c:2c:20:6f:4b:25:7c:96:61:1b:a9:57:ff:0a:5e:34:4d
(R)eject, accept (t)emporarily or accept (p)ermanently? p

I’ve upgraded the plan project limits for RoundHaus. The breakdown is as follows:

bronze_plan.number_of_projects  # => 3
bronze_plan.update_attribute(:number_of_projects, 10)  # => true

silver_plan.number_of_projects  # => 10
silver_plan.update_attribute(:number_of_projects, 25)  # => true

gold_plan.number_of_projects  # => 30
gold_plan.update_attribute(:number_of_projects, 50)  # => true

I’ve created four new screencasts showing off features of RoundHaus that you don’t get to see when playing with the demo account.

I plan on making a couple more explaining continuous integration and code coverage so stay tuned for those.

Enjoy!

Creating a New Project

Importing a Project

Creating a Campfire Signal

Creating a Twitter Signal

RoundHaus is now officially launched!

It’s been a really fun and challenging experience putting all the pieces together. From Amazon’s S3, EC2 and SQS to learning about Subversion’s Ruby Bindings. Not to mention security, backups, setting up an LLC, getting bank accounts and credit card processing.

A lot of hard work went into taking RoundHaus from the vision I had a year ago and turning it into reality. Looking back at my original vision for it amazes me to how close it actually fits what I wanted it to be and how it would work. Without the very talented and hard work of Harold Emsheimer, RoundHaus would still be a vision instead of the great application it is today. Thank you Harold.

RoundHaus has become an integral part of my development process, simplifying the mundane and letting me concentrate on developing great applications instead of worrying about setting up infrastructure.

Here’s to a productive future.

Go signup!

RoundHaus will be going down for maintenance later today in preparation for launching tomorrow. I’ll post a blurb when it goes down and when it’s back up.

Update: RoundHaus is now down for maintenance - 12:00PM EST

Update: RoundHaus is now back up - 1:00PM EST

After several months of development RoundHaus is finally ready and will be officially launched on August 8th.

Stay tuned!

RoundHaus supports giving public access to projects. You can specify on a per project basis whether or not you want to grant read-only privileges to anonymous users.

To demonstrate this capability in RoundHaus check out the Demo Account where you can browse around and check out some of the cool things that RoundHaus provides, like integrated code coverage, continuous integration for changesets and changeset diffs.

And be sure to signup! to be notified when RoundHaus goes live!

This is the fifth and final post in the series of presenting the features in RoundHaus. If you missed them here are the first, second, third and fourth in the series.

Sometimes it’s nice to be able to look at a file without having to check it out from the repository. Perhaps it is to look at a previous version of the file or maybe it is to review the code someone just checked in. RoundHaus displays beautifully highlighted code for whatever reason you are looking at it for.

Code coverage analysis is built right into the code browser so you can see if the code you are looking at has at least been executed by the testing framework.

Covered code

Uncovered code

Be sure to signup! to be notified when RoundHaus goes live.

This is the fourth in the series of posts presenting the features in RoundHaus. If you missed them here are the first, second and third in the series.

RoundHaus makes adding new people and assigning permissions to projects quick and simple.

People

The people view shows a list of all the people in the account and from there it is just a click away from adding, editing or removing people.

New Person

Adding a person to the account is equally simple. Granting a person administrator privileges lets them manage people, permissions and signals. The default permission specifies what level of access is granted to existing and new projects for the account.

Permissions

Each project has its own set of permissions for setting who can access the project and what rights they have. There are three permission levels that can be assigned.

• Does not have access to the project
• Has read-only access to the project
• Has full access to the project

Be sure to signup! to be notified when RoundHaus goes live.

This is the third in the series of posts presenting the features in RoundHaus. If you missed them here are the first and second in the series.

Signals are external applications that RoundHaus interacts with when a changeset is committed to the repository or a continuous integration process has completed. Currently RoundHaus supports four different types of Signals.

ATOM feeds

Each project in RoundHaus has its own ATOM feed of all of the changesets for that project. Also each account in RoundHaus has a single feed that contain all of the changesets for all of the projects in the account.

Campfire Signal

I use 37Signals’ Campfire application to keep in direct contact with my fellow co-workers. Any time someone checks something in to the repository we’re all notified at once.

Twitter Signal

Twitter has become a very popular way of keeping friends, family and co-workers up-to-date on what is happening right now. RoundHaus can do the same and send tweets whenever someone commits something to the repository.

Lighthouse Signal

Lighthouse is the beautifully simple issue tracking application from those ninjas over at Active Reload. Using Lighthouse Beacons, RoundHaus can send changeset notifications along with the list of files affected by the change.

Be sure to signup! to be notified when RoundHaus goes live.

This is the second post in the series of presenting RoundHaus features. The first post went over the RoundHaus Dashboard.

The project overview page is a dashboard type view for a single project. This page explains how to checkout the project from subversion, what the last three changesets are and the top 10 files in the project in order of least covered to most covered code.

For project administrators this page is where changeset notifications, called Signals, are accessed. The next post in the series will go over exactly what Signals are and what they can do.

Be sure to signup! to be notified when RoundHaus goes live.

This is the first post in a series detailing the different features of RoundHaus. So let’s get started then.

First up is the dashboard. The dashboard displays the ten most recent changesets for each of the projects a person has access to. For paying accounts each changeset displayed shows the result of the continuous integration and for successful builds the amount of code covered as reported by the excellent rcov application.

Be sure to signup! to be notified when RoundHaus goes live.

Nathaniel Talbott’s RailsConf 2006 keynote presentation of “Homesteading: A Thriver’s Guide” just ended and I left wanting to buy that ticket. I knew I wanted to go, but where? It had to be someplace that I was interested in. Some place I was passionate about. With two children and my wife competing for my limited time it had to be something that I had a personal stake in. Doing it for someone else according to their whims wasn’t going to cut it for me. Unless it’s something really great it’s hard to get passionate about someone else’s dream. I needed to make something for me. Something that I wanted and would use.

Every project I’ve worked on has had the same basic requirements of getting started. Get the source control repository up and access granted to it. Get the continuous integration working so that tests are run on the checked in code. RSS feeds and Campfire notifications so we can keep updated on what is happening. Know at a basic level what code has been executed by the testing suite. It’s not that any of this is difficult to setup. It’s just error prone, repetitive and cumbersome. Three adjectives that typically strike a nerve with programmers. It certainly bothers me.

When I get started on a project I want to jump right in. Get that problem solved and that code out there. Release early, release often and all that. Having to go through the somewhat painful task of going through the setup motions every project is one itch that I decided to scratch.

RoundHaus is my attempt to scratch that itch. Make it easy to get started and easy to stay on top of it. I don’t think I’m the only one with this particular itch so hopefully it will be a great help to others as well. I’m buying that ticket. Only time will tell if the destination pans out.

Be sure to signup! to be notified when RoundHaus goes live.