From 69afda758ba7970e8ebd086763b2b8236285ee46 Mon Sep 17 00:00:00 2001 From: Rob Weber Date: Mon, 13 Oct 2014 14:33:47 -0500 Subject: [PATCH] updated readme for google drive --- README.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.txt b/README.txt index 11efe87..676d74f 100644 --- a/README.txt +++ b/README.txt @@ -36,6 +36,11 @@ Using Dropbox as a storage target adds a few steps the first time you wish to ru Once you have your app key and secret add them to the settings. XBMC Backup now needs to have permission to access your Dropbox account. When you see the prompt regarding the Dropbox URL Authorization DO NOT click OK. Check your XBMC log file for a line from "script.xbmcbackup" containing the authorization URL. Cut/paste this into a browser and click Allow. Once this is done you can click "OK" in XBMC and proceed as normal. XBMC Backup will cache the authorization code so you only have to do this once, or if you revoke the Dropbox permissions. +Using Google Drive: + +Using the Google Drive target is very similiar to the Dropbox one. You must create a Google API project and authenticate your account via the id and secret. Instructions for creating the Google API for Google Drive can be found here. You'll need the client id and client secret generated for the addon settings (https://developers.google.com/drive/web/quickstart/quickstart-python). You only need to follow Step 1. + +Once you have the client ID and Secret add them to the addon settings and run a backup. You'll get a notification that you need to enter your authorization code. Check your XBMC log file for a line from "script.xbmcbackup" containing the authorization URL. Cut/paste this into a browser and click Allow. Once this is done put the code from your browser into the pop-up dialog. The addon will cache these credentials so it should be a one-time authenication. From there the backup should start to run. Scripting XBMC Backup: