Bug#525350: [rt.cpan.org #45261] Hardcoded s3 Server Name

[Joey Hess via RT]

<URL: https://rt.cpan.org/Ticket/Display.html?id=45261 >

On Tue Mar 30 06:43:17 2010, LBROCARD wrote:
> I can't develop this without testing and it is somewhat non-trivial to
> install Eucalptus.
> 
> There seem to be a bunch of changes that have to be made, looks like
> we'll have to disable DNS buckets amongst other things:
> 
> http://www.jamesmurty.com/2009/04/30/how-to-use-jets3t-with-
eucalyptus/
> 
> I'm very willing to accept patches. Alternatively, if you could set me
> up an account on a public Eucalptus instance then I would work on it.
> 
> Regards, Leon

Leon, I never successfully applied for a Eucalyptus account either. My 
signup to the Eucalyptus Public Cloud sandbox never seemed to go 
anywhere.

However, I just learned that archive.org has a s3 compatible server as 
well. It can be used by anyone who signs up for an archive.org account, 
which can be done easily. http://www.archive.org/help/abouts3.txt

Also, the current rumor is that Google is launching a S3 competator, and 
it seems likely it will offer a compatable API to S3.

I'd be happy with a dehardcoded hostname so I could use the perl 
libraries against anything. If a feaure is not supported (like 
archive.org doesn't support DELETE :) I'd be happy if attempt to use it 
failed. No need to special-case things.