A client implementation for Rackspace CloudFiles in node.js
$ curl | sh
$ npm install cloudfiles
The node-cloudfiles library is compliant with the Rackspace CloudFiles API. Using node-cloudfiles is easy for a variety of scenarios: authenticating, creating and working with both containers and storage objects.
Before we can do anything with cloudfiles, we have to create a client with valid credentials. Cloudfiles will authenticate for you automatically:
var cloudfiles = ;var config =auth :username: 'your-username'apiKey: 'your-api-key';var client = cloudfiles;
Rackspace Cloudfiles divides files into 'Containers'. These are very similar to S3 Buckets if you are more familiar with Amazon. There are a couple of simple operations exposed by node-cloudfiles:
// Creating a containerclient;
Each Container has a set of 'StorageObjects' (or files) which can be retrieved via a Cloudfiles client. Files are downloaded to a local file cache that can be configured per client.
Use the 'host' key in the auth configuration to specify the url to use for authentication:
var cloudfiles = ;var config =auth :username: 'your-username'apiKey: 'your-api-key'host : "lon.auth.api.rackspacecloud.com";var client = cloudfiles;
Rackspace Cloud Servers have a private interface, known as ServiceNet, that is unmetered and has double the throughput of the public interface. When transferring files between a Cloud Server and Cloud Files, ServiceNet can be used instead of the public interface.
By default, ServiceNet is not used. To use ServiceNet for the transfer, set the 'servicenet' key to
true in your client config:
var cloudfiles = ;var config =auth :username: 'your-username'apiKey: 'your-api-key'host : "lon.auth.api.rackspacecloud.com"servicenet: true;var client = cloudfiles;
NOTE: ServiceNet can only be used to transfer files between Cloud Servers and Cloud Files within the same datacenter. Rackspace support can migrate both Cloud Servers and Cloud Files to the same datacenter if needed.
All of the node-cloudservers tests are written in vows, and cover all of the use cases described above. You will need to add your Rackspace API username and API key to test/fixtures/test-config.json before running tests:
"auth":"username": "your-username""apiKey": "your-apikey"
Once you have valid Rackspace credentials you can run tests with vows:
vows test/*-test.js --spec