Google Drive client with support for new Drive REST API and partial sync http://yourcmc.ru/wiki/Grive2
 
 
 
 
 
Go to file
Nestal Wan 27817e835f using the new Json classes for bgrive 2013-05-03 00:40:04 +08:00
bgrive added Val class for generic representation of JSON, but there's some problems with maps 2013-05-01 01:56:34 +08:00
cmake/Modules use libgcrypt instead of OpenSSL 2012-06-05 22:51:54 +08:00
grive refactored old GDoc API into v1 namespace. using v2 namespace for new Google Drive API 2013-04-29 23:47:33 +08:00
icon thanks Chris Goodman for contributing the icons! 2012-04-26 17:26:04 +08:00
libgrive using the new Json classes for bgrive 2013-05-03 00:40:04 +08:00
package/fedora16 updated RPM spec to point to latest version 2012-06-09 15:32:54 +08:00
.gitignore Revert "Revert "Ignore DS_STORE"" 2012-05-26 22:23:43 +01:00
CMakeLists.txt refactored exception handling 2013-04-29 23:47:32 +08:00
COPYING updated the readme file and added GPLv2 license 2012-05-02 23:43:39 +08:00
README clean up on #109 2012-07-30 15:24:47 +08:00

README

Grive 0.3.0
25 July 2012

http://www.lbreda.com/grive/

Grive can be considered still beta quality. It simply downloads all the files in your
Google Drive into the current directory. After you make some changes to the local files, run
grive again and it will upload your changes back to your Google Drive. New files created locally
or in Google Drive will be uploaded or downloaded respectively. Deleted files will also be "removed".
Currently Grive will NOT destroy any of your files: it will only move the files to a
directory named .trash or put them in the Google Drive trash. You can always recover them.

There are a few things that Grive does not do at the moment:
- wait for changes in file system to occur and upload. A sync is only performed when you run Grive.
- symbolic links support
- support for Google documents
  
Of course these will be added in the future, possibly the next release.

You need the following libraries:

- json-c
- libcurl
- libstdc++
- libgcrypt
- Boost (Boost filesystem and program_option are required)

There are also some optional dependencies:
- CppUnit (for unit tests)
- libbfd (for backtrace)
- binutils (for libiberty, required for compilation in OpenSUSE & ubuntu)

Grive uses cmake to build, see the instructions in:

http://www.lbreda.com/grive/installation

...for detailed procedures to compile Grive.

When Grive is run for the first time, you should use the "-a" argument to grant
permission to Grive to access to your Google Drive. A URL should be printed.
Go to the link. You will need to login to your Google account if you haven't
done so. After granting the permission to Grive, the browser will show you
an authenication code. Copy-and-paste that to the standard input of Grive.

If everything works fine, Grive will create .grive and .grive_state files in your
current directory. It will also start downloading files from your Google Drive to
your current directory.

Enjoy!

Version History:

Grive v0.3: Bug fix & minor feature release
Fixed bugs:
	#93: missing reference count increment in one of the Json constructors
	#82: retry for HTTP error 500 & 503
	#77: Fixed a bug where grive crashed on the first run.

New features:
	#87: support for revisions
	#86: partial sync (contributed by justin at tierramedia.com)