Merge lp:~user3942934/duplicity/pydrive into lp:~duplicity-team/duplicity/0.7-series
Proposed by
westerngateguard
Status: | Merged |
---|---|
Merged at revision: | 1054 |
Proposed branch: | lp:~user3942934/duplicity/pydrive |
Merge into: | lp:~duplicity-team/duplicity/0.7-series |
Diff against target: |
202 lines (+149/-2) 4 files modified
bin/duplicity.1 (+40/-1) duplicity/backend.py (+1/-1) duplicity/backends/pydrivebackend.py (+107/-0) duplicity/commandline.py (+1/-0) |
To merge this branch: | bzr merge lp:~user3942934/duplicity/pydrive |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+246258@code.launchpad.net |
Description of the change
Hello,
Currently duplicity uses gdocs backend for Google Drive backups.
gdocs uses deprecated API and don't allow backups for managed Google accounts.
(see https:/
I added pydrive backend that solves both of those problems. I published it also on GitHub: https:/
It works fine on my Debian (Wheezy) machine.
To post a comment you must log in.
I think you accidentally deleted some azure documentation from the man page?
Also, you use a keyfile specified by the URL. But all of the other backends tend to use environment variables for that sort of thing. Is there a reason you went with a file?