![]() ![]() ![]() Smaller values mean more API calls for presence check of big files which can dramatically slow down fsck, drop or move. If you use it, a value between 50MiB and 500MiB is probably a good idea. If you don't use either of those on this remote, you can just ignore this option. If you want to access a file while it's still being downloaded using git-annex-inprogress If you're using encryption, this is the amount of disk space that will additionally be used during upload. ![]() As Google Drive allows file sizes up to 5TB and as this remote implements chunked transfers, this option is actually only useful in two situations: (1) Encryption. chunk - This is the size in which git-annex splits the keys prior to uploading, see chunking.It will not be usable as a general-purpose special remote. exporttree - Set to yes to make this special remote usable by git-annex-export.keyid - Specifies the gpg key to use for encryption.encryption - One of "none", "hybrid", "shared", "pubkey" or "sharedpubkey".Bigger values create slightly less overhead and are therefore somewhat more efficient. Smaller values meaning less data to be re-transmitted when network connectivity is interrupted and result in a finer progress feedback. A value between 1MiB and 10MiB is recommended. This is the minimum data which has to be retransmitted when resuming after a connection error. transferchunk - Chunksize used for transfers.auto_fix_full - Set to yes if the remote should try to fix full-folder issues automatically.Imported to layout in case you're migrating from a different remote.) (Existing settings for gdrive_layout or rclone_layout are automatically git-annex-remote-googledrive will migrate automatically. Available options: nested(default), nodir, lower and mixed. layout - How the keys should be stored in the remote folder.Can also be used to access shared folders which you haven't added to "My Drive". This will make it independent from the path and it will always be found by git-annex, no matter where you move it. root_id - Instead of the path, you can specify the ID of a folder.prefix - The path to the folder that will be used for the remote.Options specific to git-annex-remote-googledrive To debug issues, use the -debug flag, i.e. The initremote command calls out to GPG and can hang if a machine has insufficient entropy. Git annex initremote google type=external externaltype=googledrive prefix=git-annex encryption=shared mac=HMACSHA512 Stores your files in a folder/prefix called git-annex:.Encrypts all chunks prior to uploading and stores the key within the annex repository.In the repository, run git-annex-remote-googledrive setup and follow the instructions to authenticate with your Google account.Īdd a remote for Google Drive. Pip3 install git-annex-remote-googledriveįor Arch Linux, there is a package available in the AUR UsageĬreate a git-annex repository ( walkthrough) using different Google accounts simultaniously (even within the same repository).storing the credentials within the repository.This might affect access to your remotes. IMPORTANT: Google has started to lockdown their Google Drive API. Git-annex-remote-googledrive adds direct and fast support for Google Drive to git-annex and comes with some awesome new features. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |