[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Deprecation of pydrivebackend
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Deprecation of pydrivebackend |
Date: |
Wed, 21 Jun 2023 16:52:37 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 |
On 21.06.2023 15:50, Jakob Bohm via Duplicity-talk wrote:
Dear Duplicity team,
hey Jakob
For everyone except the few insiders participating in today's
discussion, it is important to ensure that all explanation
texts in manpage etc. do not assume facts not provided where
that text is.
In particular:
A. The manpage snippet below refers to "the downloaded JSON", but
not when and where that download would come from. If this is
part of unchanged text above that sentence then fine.
feel free to contribute a better documentation. nobody here is getting paid and
everything is done on a voluntary basis.
B. Discussions elsewhere seem to assume that everyone using GDrive
does so via a developer account. Please update text (without
unstated assumptions) for ordinary users, including warning if
this is somehow against Google Policy.
which discussions? i don't see Google policy violations, what do you mean
exactly?
C. Elsewhere William asks for migration instructions and got a
reply about "If he already did X", which is clearly specific to
William and not a part of any migration recipe that could be
used by others once the old URL Scheme is deprecated as indicated
by the thread subject.
obviously the "migration instructions" as such do not exist. that is why he was
referred to what little as documentation is available.
P.S.
I happen to be currently using AWS S3 glacier via the boto3 code,
and find similar readability problems in that documentation,
same principle applies. if you are dissatisfied you are welcome to be part of a
solution. general complaints will improve nothing.
hence this mail about general principles seemingly about to get
similarly mishandled for Google users.
and again, please handle it better, if you feel inclined to. we are lacking
human power all over and it unfortunately shows.
sunny regards.. ede
On 2023-06-20 14:36, Chris McGinley via Duplicity-talk wrote:
Thanks Edgar.
Here are some thoughts on the GDRIVE man page notes (I used the Google My Drive
approach with a regular user account) -
1. The target URL can be found in the downloaded JSON (i.e.,
*GOOGLE_CLIENT_SECRET_JSON_FILE*) as the client_id property.
2. *MyDriveFolderID* can be found by observing the URL when accessing your
destination folder
For example:
/gdrive://11111111-ab123cd456ef789.apps.googleusercontent.com/mylaptop?myDriveFolderID=xyz987uvw654/
* where /11111111-ab123cd456ef789.apps.googleusercontent.com/ was found in
the downloaded JSON file, /xyz987uvw654/ is the parent folder ID found from
browsing to Google Drive /backups/ folder, and /mylaptop/ is a subfolder of
/backups/
Also note, if migrating from pydrive, do not point
*GOOGLE_CREDENTIALS_FILE* at the pydrive credential file; it should point to a
new (and non-existing) file destination.
Best.
Chris
On Tuesday, June 20, 2023 at 07:56:28 AM EDT, <edgar.soldin@web.de> wrote:
we welcome suggestions to improve documentation. if you provide some textual
changes based on your experience we will happily include them in the man page.
..ede
On 20.06.2023 13:54, Chris McGinley wrote:
> I was able to make the move over to gdrive after sending over my response.
The DriveID, MyDriveFolderID, and the destination URL were not entirely obvious to
me from the man page notes; however, with some trial and error, I was able to get
it all working.
>
> -Chris
>
>
> On Tuesday, June 20, 2023 at 06:41:00 AM EDT, edgar.soldin--- via Duplicity-talk
<duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:
>
>
> hey WIlliam,
>
> how about following the instructions in the man page? :)
> https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend
<https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend>
<https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend
<https://duplicity.us/stable/duplicity.1.html#a-note-on-gdrive-backend>>
>
> good luck ..ede/duply.net
>
> On 19.06.2023 18:53, William via Duplicity-talk wrote:
> > I have been using pydrive for 6+ years, as documented in the V8 manual
page (https://duplicity.nongnu.org/vers8/duplicity.1.html).
> >
> > No mention there that pydrive is not to be used.
> >
> > Is there a cookbook instructions on how to convert the pydrive
commands/setup to gdrive.
> >
> > I use DUPLY to drive the backups, so the necessary EXPORT and file specs
are in the DUPLY conf file.
> >
> >
> > On 6/19/23 11:59, Kenneth Loafman via Duplicity-talk wrote:
> >> Hi all,
> >>
> >> Does anyone use the pydrive backend anymore? This would be a URL schema of "pydrive://",
"pydrive+gdocs://" or "gdocs://"
> >>
> >> It was replaced with the gdrive backend a couple of years ago. Before we
deprecate it I was just trying to find out if there was anyone still using it. And how?
> >>
> >> ...Thanks,
> >> ...Ken
> >>
> >>
> >> _______________________________________________
> >> Duplicity-talk mailing list
> >> Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
<mailto:Duplicity-talk@nongnu.org>
> >> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>>
> >
>
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
<mailto:Duplicity-talk@nongnu.org>
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>>
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
- [Duplicity-talk] Deprecation of pydrivebackend, Kenneth Loafman, 2023/06/19
- Re: [Duplicity-talk] Deprecation of pydrivebackend, William, 2023/06/19
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Kenneth Loafman, 2023/06/19
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Chris McGinley, 2023/06/19
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Chris McGinley, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Chris McGinley, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Jakob Bohm, 2023/06/21
- Re: [Duplicity-talk] Deprecation of pydrivebackend,
edgar . soldin <=
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Jakob Bohm, 2023/06/22
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/22
- Re: [Duplicity-talk] Deprecation of pydrivebackend, Kenneth Loafman, 2023/06/23
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/23
- Re: [Duplicity-talk] Deprecation of pydrivebackend, William, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, William, 2023/06/20
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/21
- Re: [Duplicity-talk] Deprecation of pydrivebackend, edgar . soldin, 2023/06/21