-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Drive remote documentation #381
Comments
|
@dmpetrov may have a better understanding if GDrive backend would be heavily used by something like a webinar or class lessons in the groups of students... Probably 10+ users syncing a big repo would affect each other, so maybe we have to give the instructions for the teachers to recommend to use the separate client tokens per student in such scenarios. |
We also can go to the dark side and create some client tokens in advance, and chose between them randomly :). // but this is why google wouldn't be restrictive in quota extension inquiries, so never mind |
@ei-grad makes sense, thanks! |
Just creating the docs issue for the upcoming iterative/dvc#2040 which would bring the Google Drive support.
Some things to mention:
There are 3 types of URLs:
Subfolder in the "My Drive" folder:
Folder by ID (recommended):
(get it from the last part of URL https://drive.google.com/drive/folders/{here})
Dataset named "my-dataset" in the hidden application folder:
(this one wouldn't be visible through Google Drive web UI and
couldn't be shared)
OAuth2, client ID and quotas, we need something like this: https://rclone.org/drive/#making-your-own-client-id
There is an
oauth_id
option in remote config section, which could contain arbitary identifier and is meant to be used to allow different Google user accounts usage for different remotes.The text was updated successfully, but these errors were encountered: