Jesse Peterson

I have successfully used S3Fox Organizer with the current “littles3” source code. S3Fox Organizer is a Firefox extension which provides a simple interface for managing files with Amazon S3. To get it to work, I needed to control the resolving of “http://s3.amazonaws.com”, which is the URL that S3Fox Organizer is coded to use. I edited my machines “hosts” file, C:\WINDOWS\system32\drivers\etc\hosts on Windows, to have s3.amazonaws.com resolve to 127.0.0.1, localhost. I have “littles3″ running within Tomcat. I have it running as the “ROOT” application so that there is no application context. I also have Apache running with mod_jk connecting to Tomcat.

This definitely takes advanced skills to get running and “littles3″ isn’t complete yet, but this is a good integration test. The current “littles3″ source code has ACL support now. It still needs to implement metadata and the ability to “provision” user accounts. But it is at a personally usable state now.

I have launched a project, “littles3“, on Google Code. This project is a Java web application which provides a storage service based on the Amazon Simple Storage Service (Amazon S3) API.

So far, I have implemented a StorageEngine which stores content to the local file system. It currently does the basic storage function outlined in the S3 api. What isn’t implemented yet?

1. ACL
2. Custom metadata

Why am I doing this? I think that Amazon S3 is a pretty neat thing. It provides hosted storage at a very reasonable rate. But there may be times when you want to store your data locally but still use the Amazon S3 API. This server will do that.