googledriveannex 0.2.0

Hook program for gitannex to use Google Drive as backend

Requirements:

python2
python-httplib2

Credit for the googledrive api interface goes to google

Install

Clone the git repository in your home folder.

git clone git://github.com/TobiasTheViking/googledriveannex.git 

This should make a ~/googledriveannex folder

Setup

Make the file executable, and link it into PATH

cd ~/googledriveannex; chmod +x git-annex-remote-googledrive; sudo ln -sf `pwd`/git-annex-remote-googledrive /usr/local/bin/git-annex-remote-googledrive

Commands for gitannex:

git annex initremote googledrive type=external externaltype=googledrive encryption=shared folder=gitannex

An oauth authentication link should now be launched in the default browser. Authenticate and you will be proved with a code.

OAUTH='authentication code' git annex initremote googledrive type=external externaltype=googledrive encryption=shared folder=gitannex
git annex describe googledrive "the googledrive library"
I have now configured my Googledrive on Laptop1 according to the guide above, how do I add the same remote on Laptop2? It would be nice if this was described in the guide, include where the encryption keys are stored.

Hi,

I am new to git-annex and I want to use google drive as remote but I can't.

I create syslink to googledriveannex in /usr/local/bin.

When I execute below command, command waiting but not make anything:

$ git annex initremote googledrive type=external externaltype=googledrive encryption=shared folder=gitannex

initremote googledrive (encryption setup) # Waiting but does not do anything.

What I am doing wrong?

Thanks for helps

@Mesut, I think you're doing everything right. It can take a long time for the highly secure gpg key to be generated. Sit tight and let it finish, or you can pass --fast to generate a key that is a tiny bit less secure.
Comment by http://joeyh.name/ Thu Apr 17 20:58:41 2014

Hi Johnny,

I wrote a patch for googledriveannex that fixed this problem for me. First you add the google drive special remote in repo1 then you clone repo1 into repo2. In repo2 you do "git annex enableremote googldrivespecialremotename" and it should work. The problem was that the init method, that is called by git annex when a special remote is first created but also when it is enabled somewhere else, did not factor in the possibility that it had already been created. I will simultaneously submit the patch to the author of the special remote plugin but here it is for you to quickly get going:

diff --git a/git-annex-remote-googledrive b/git-annex-remote-googledrive
index 49cd917..c8e70f3 100755
--- a/git-annex-remote-googledrive
+++ b/git-annex-remote-googledrive
@@ -330,13 +330,16 @@ def initremote(line):
     oauth = os.getenv("OAUTH") or ""
     encryption = common.getConfig("encryption")
     myfolder = common.getConfig("folder")
-    stored_creds = sys.modules["__main__"].login({"oauth": oauth})
-    if len(myfolder) and stored_creds:
-        common.sprint('SETCONFIG myfolder ' + myfolder + '')
-        common.sprint('SETCONFIG stored_creds ' + json.dumps(stored_creds) + '')
-        common.sprint('INITREMOTE-SUCCESS')
+    if not common.getConfig("stored_creds"):
+       stored_creds = sys.modules["__main__"].login({"oauth": oauth})
+       if len(myfolder) and stored_creds:
+           common.sprint('SETCONFIG myfolder ' + myfolder + '')
+           common.sprint('SETCONFIG stored_creds ' + json.dumps(stored_creds) + '')
+           common.sprint('INITREMOTE-SUCCESS')
+       else:
+           common.sprint('INITREMOTE-FAILURE You need to set OAUTH environment variables and folder and encryption parameters when running initremote.')
     else:
-        common.sprint('INITREMOTE-FAILURE You need to set OAUTH environment variables and folder and encryption parameters when running initremote.')
+           common.sprint('INITREMOTE-SUCCESS')
     common.log("Done")

 def prepare(line):
-- 
Comments on this page are closed.