Gdrive Games

0 views

Skip to first unread message

Jomega Gibson

unread,

Aug 3, 2024, 3:03:54 PM8/3/24

to centgeabvixer

There are problems still with kio-gdrive, I tried to use it and I could not log in my google account to reproduce the issue because the authentication did not accept the embedded browser we are currently using for this.

please provide the cmd command for backup file from gdrive to s3 bucket using kopia by integrating rclone.i have finished configuring both drive and s3 . what is the next step can anyone guide us through

I'm having the same issue. I can not export or save the file from my Ipad to the google drive. When I open the files and go to google drive, I can see the files there but they are grayed out with a red circle with a white line. It doesn't even work when I export it as a PNG. Same thing gray file with red circle and white line. Was there a fix for this?

This is exactly what I'm trying to do on mine, but google drive is grayed out. Going back up the thread, seems like it worked for a few people but not everyone. What version of iOS are you using? Did you do anything special with the authentication settings on gdrive? I would like to get this working and so far haven't heard anything from official support...

@Dan C Ok, I just uninstalled both Drive and Affinity Designer, updated to the latest iOS (14.4), reinstalled drive, then reinstalled Affinity. I also from the Drive app went to Settings and turned off Privacy Screen, to see if that helped. None of it made a difference at all (apart from deleting my custom swatches and brushes, luckily I backed up my work before deleting Affinity).

iPadOS 13.1 has changed from previous versions by greying out any third party drive that haven't supported their API completely. This requires the third party to support the Files API properly, as this export path from Affinity requires 'Folder Output' support, which is only officially supported in iPadOS 13."

I have also been able to replicate the above, and I don't believe this has been logged previously. I'm not entirely certain for the cause of this, perhaps it's related to the permissions written to the file.

To start using a Google Drive remote, you only need to add it with avalid URL format. Then use any DVC command that needs to connectto it (e.g. dvc pull or dvc push once there's tracked data to synchronize).For example:

GDrive remotes are not "trusted" by default. This means that theverifyparameter is enabled on this type of storage, so DVC recalculates the filehashes upon download (e.g. dvc pull), to make sure that these haven't beenmodified.

DVC uses the Google Drive API to synchronize your DVC project data with thistype of remote storage, so it's subject to certain usage limits and quotas,which by default are shared with other GDrive remote storage users. For heavyuse, it's highly recommended toconnect using a custom Google Cloud project,which puts you in control of these limits.

There's a few alternatives to construct a GDrive remote URL for different uses,such as a folder or subfolder in root, shared folders not owned by your account,etc. The URL is formed with a base, and an optional path to an existingfolder i.e. gdrive:///path/to/folder. The base can be one of:

Optionally, follow these steps to create your own Google Cloud project andgenerate OAuth credentials for your GDrive remotes to connect to Google Drive.We highly recommend this for heavy use and advanced needs because:

DVC uses the Google Drive API to connectto your Google Drive. This requires a Google Cloud project that allows DriveAPI connections, and itsOAuth credentials(client ID and client secret).

This covers simple authentication, which gives DVC access to GDrive on behalf ofa user account. This is ideal to use to run DVC locally, for example. If someautomation is needed (e.g. CI/CD) we recommendusing a service account instead.

Alternatively, a GDRIVE_CREDENTIALS_DATA can be set to pass user credentialsin CI/CD systems, production setup, read-only file systems, etc. The content ofthis variable should be a string with JSON that has the same format as in thecredentials files described above, and usually you get it going through the sameauthentication process. If GDRIVE_CREDENTIALS_DATA is set, thegdrive_user_credentials_file value (if provided) is ignored.

A service account is aGoogle account associated with your GCP project, and not a specific user. Theyare intended for scenarios where your code needs to access data on its own, e.g.running inside a Compute Engine, automatic CI/CD, etc. No interactive user OAuthauthentication is needed.

Google service accounts have their own associated usage limits which may beexceeded if used frequently in conjunction with dvc push, dvc pull, etc. Forheavy usage, it is recommended to rely ondelegation.

Alternatively, a GDRIVE_CREDENTIALS_DATA can be set to pass service accountkey in CI/CD systems, production setup, read-only file systems, etc. Thecontent of this variable should be a string with JSON that has the sameformat as in the keys file described above. If both this variable andgdrive_service_account_json_file_path are provided,GDRIVE_CREDENTIALS_DATA takes priority andgdrive_service_account_json_file_path is ignored.

Share the Google Drive folders that you want to use with the service account.Navigate to your Google Drive folder's sharing options and add the serviceaccount as an editor (read/write) or viewer (read-only):

gdrive_trash_only - configures dvc gc to move remote files totrashinstead ofdeletingthem permanently. false by default, meaning "delete". Useful for shareddrives/folders, where delete permissions may not be given.

gdrive_acknowledge_abuse - acknowledge the risk of downloading potentiallyabusive files. Anythingidentified as such (malware, personal info., etc.) can only be downloaded bytheir owner (with this param enabled).