Can Camlistore use Google Drive storage via the Drive API?

[Todd Larsen]

Has anyone tried to use Google Drive storage as a place for Camlistore blobs to be stored?

[Mathieu Lonjaret]

Not the same thing, but fwiw we already have an issue opened for
google cloud storage
https://code.google.com/p/camlistore/issues/detail?id=23

On 18 April 2013 21:52, Todd Larsen <todd....@gmail.com> wrote:
> Has anyone tried to use Google Drive storage as a place for Camlistore blobs
> to be stored?
>

> --
> You received this message because you are subscribed to the Google Groups
> "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to camlistore+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Todd Larsen]

On Thu, Apr 18, 2013 at 2:38 PM, Mathieu Lonjaret
<mathieu....@gmail.com> wrote:
> Not the same thing, but fwiw we already have an issue opened for
> google cloud storage
> https://code.google.com/p/camlistore/issues/detail?id=23

Yes. I understand how Google Cloud Storage would be the highest
priority. I'm just wondering how to make use of that Google Drive
storage that comes for free with a Chromebook. :)

The interesting use case might be some sort of Chrome browser
extension that could access Camlistore blobs from Google Drive
storage. Another interesting use case is backing up local Camlistore
blobs to that Google Drive quota.

[Simon B.]

On Friday, April 19, 2013 at 12:16:47 AM UTC+2, Todd Larsen wrote:

On Thu, Apr 18, 2013 at 2:38 PM, Mathieu Lonjaret
<mathieu....@gmail.com> wrote:
> Not the same thing, but fwiw we already have an issue opened for
> google cloud storage
> https://code.google.com/p/camlistore/issues/detail?id=23

[...]

Another interesting use case is backing up local Camlistore
blobs to that Google Drive quota.

Rarely changing blobs could be mirrored using any existing tools (rsync, scp, any API:s - and on Google Cloud there is a lower tariff for long-term storage, rarely accessed blobs) but often changing roots etc are probably most practical to just keep on all clients.
To understand if/how this applies to camli, I sense a need for simpler step-by-step documentation. I've spent over 2 hours reading docs and code, watching prezi's and experimenting, and am not yet ready to keep any important data only in camli. I'm interested in making the onboarding more streamlined for incoming potential users that come after me.