Comments on: Posting gems to Rubyforge http://www.3hv.co.uk/blog/2009/10/06/posting-gems-to-rubyforge/ precision engineering for your website Sat, 14 Jan 2012 00:39:13 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Rahoul Baruah http://www.3hv.co.uk/blog/2009/10/06/posting-gems-to-rubyforge/comment-page-1/#comment-1462 Rahoul Baruah Wed, 07 Oct 2009 04:23:30 +0000 http://www.3hv.co.uk/blog/?p=588#comment-1462 I'm not in any way slagging off gemcutter - I like it. But it's young and has a single point of failure. If Geoffrey Grosenbach, for whatever reason, decides to close his S3 account down then that means I can't get access to his stuff. Peepcode customers have a dependency on Geoffrey. If Nick decides to close his S3 account down (or Amazon screws up billing and closes his account or even worse, he gets hit by a bus), it's not just me that's affected - anyone who uses this gem (our customers) have a dependency on Nick. If it was my personal stuff it wouldn't matter, but it's not - it's work stuff . And yes, they can grab the source off Github - but the reason the release was delayed in the first place was because we were relying on Github - so it's about spreading the load. (Plus a Rubyforge mirror happens to be available on one of our bandwidth providers, which is nice). I can see from the mailing list replies that Nick is looking into the mirroring; but it's not here TODAY and this release was already late. I’m not in any way slagging off gemcutter – I like it. But it’s young and has a single point of failure.

If Geoffrey Grosenbach, for whatever reason, decides to close his S3 account down then that means I can’t get access to his stuff. Peepcode customers have a dependency on Geoffrey.

If Nick decides to close his S3 account down (or Amazon screws up billing and closes his account or even worse, he gets hit by a bus), it’s not just me that’s affected – anyone who uses this gem (our customers) have a dependency on Nick.

If it was my personal stuff it wouldn’t matter, but it’s not – it’s work stuff . And yes, they can grab the source off Github – but the reason the release was delayed in the first place was because we were relying on Github – so it’s about spreading the load.

(Plus a Rubyforge mirror happens to be available on one of our bandwidth providers, which is nice).

I can see from the mailing list replies that Nick is looking into the mirroring; but it’s not here TODAY and this release was already late.

]]> By: Nick Quaranto http://www.3hv.co.uk/blog/2009/10/06/posting-gems-to-rubyforge/comment-page-1/#comment-1461 Nick Quaranto Wed, 07 Oct 2009 02:25:22 +0000 http://www.3hv.co.uk/blog/?p=588#comment-1461 You basically just described one of the main reasons why I started Gemcutter. If you've got any qualms about the service (besides this about S3), let me know, I'll be glad to help ease them. :) You basically just described one of the main reasons why I started Gemcutter. If you’ve got any qualms about the service (besides this about S3), let me know, I’ll be glad to help ease them. :)

]]> By: Eric Hodel http://www.3hv.co.uk/blog/2009/10/06/posting-gems-to-rubyforge/comment-page-1/#comment-1460 Eric Hodel Wed, 07 Oct 2009 02:15:32 +0000 http://www.3hv.co.uk/blog/?p=588#comment-1460 What does "one guy's S3 account" have to do with it? Peepcode is hosted off one guy's S3 account, as are many other successful websites. What does “one guy’s S3 account” have to do with it?

Peepcode is hosted off one guy’s S3 account, as are many other successful websites.

]]>