perkeep

History

Burcu Dogan 6e6e910af1 Adding Google Drive as a storage backend experimentally. No cheap-enough way of enumerating Drive files, needs to be fixed once Drive supports range queries. Allows you to sync to /sto-googledrive/, but not from. Change-Id: I6ac5ef02c5f51a6abdab5c207a3a5693c6bb8581		2013-08-17 15:30:02 +02:00
..
testdata	Update from r60 to [almost] Go 1.	2012-02-18 21:53:06 -08:00
README	Adding Google Drive as a storage backend experimentally. No cheap-enough way	2013-08-17 15:30:02 +02:00
auth.go	issue 23: Fix google storage blobserver as sync dest	2013-07-08 11:33:10 -05:00
googlestorage.go	issue 23: Fix google storage blobserver as sync dest	2013-07-08 11:33:10 -05:00
googlestorage_test.go	issue 23: Fix google storage blobserver as sync dest	2013-07-08 11:33:10 -05:00

README

Implements the Storage interface for Google Storage.
A GoogleStorage instance stores blobs in a single Google Storage bucket, with
each blob keyed by its blobref.  

Server configuration
=====================

High-level server config is formatted like:

	"googlecloudstorage": "clientId:clientSecret:refreshToken:bucketName"


Testing
========

googlestorage_test.go contains integration tests which run against Google Storage.
In order to run these tests properly, you will need to:

1.  Set up google storage.  See:
	http://code.google.com/apis/storage/docs/signup.html

2.  Upload the contents of the testdata dir to a google storage bucket.  Note
	that all these files begin with 'test-': such files will be ignored when 
	the bucket is used as blobserver storage.

3.  Create the config file '~/.config/camlistore/gstestconfig.json'.  The 
    file should look something like this:

	{
		"gsconf": {
			"auth": {
				"client_id": "your client id",
				"client_secret": "your client secret",
				"refresh_token": "a refresh token"
			},
			"bucket": "bucketName"
		}
	}


	You can use 'camtool gsinit' to help obtain the auth config object.