Daikini

RoundHaus will be shutting down effective December 1, 2008. RoundHaus was created to fill a need for super simple repository hosting and notifications since nothing at the time offered the polish and integration I was looking for. Unfortunately RoundHaus has not taken off like I would have liked. At the same time, several quality hosting providers have since launched and the popularity of git has exploded leaving subversion only hosting in a decline for the market RoundHaus was targeting. It does not make sense for me to continue RoundHaus with the limited amount of time and money I have to dedicate to it.

Here is a list of hosting providers I recommend checking out:

Subversion Hosting

• Beanstalk
• Unfuddle

Git Hosting

• GitHub
• CodeBase
• Unfuddle

If you have any questions or comments please do not hesitate to contact me.

Best Regards,

Jonathan Younger

RoundHaus is now down for maintenance as it’s being relocated to Amazon EC2.

Will update when it is back up and running.

UPDATE 11:57PM EST: RoundHaus has now been migrated over and is fully functional.

What: Moving hosting provider to the EC2 cloud at Amazon

When: Wednesday, August 27th, 11PM EST

Downtime: Approximately 3 hours

To increase reliability of RoundHaus services, RoundHaus will be moving to Amazon’s EC2 service from the current hosting provider.

It may take some time for the DNS update to propagate across the internet so it might be advisable to update your hosts file with the new RoundHaus IP Address of 75.101.131.54. Both svn.roundhaus.com and your individual domain name of domain.roundhaus.com should point to this new address.

In addition, subversion may once again prompt with the “Error validating server certificate message” when accessing svn.roundhaus.com. It’s ok to go ahead and (p)ermanently accept this new certificate.

For status updates you can follow us at http://twitter.com/roundhaus.

Please contact support at roundhaus.com if you have any concerns or questions.

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 had an unbelievable time at MountainWest RubyConf this year. I’d say it was by far the most enjoyable conference I’ve been to.

The slides and demo application for my presentation “Using Amazon’s Webservices From Ruby” are available on github.

I believe the video for the presentation will be available from Confreaks later this week. I’ll update the post with a link when I get it. You’ll be able to get to videos of all the presentations here when they are ready.

UPDATE 04/03/2008: Presentation is now available.