5995eba531
In several cases, there's an old, maybe unmaintained special remote, and rclone also supports the service. I don't know which is better, so I added tips pages for these, listing both possibilies, so users can fill in the details. Added some things listed in special_remotes/rclone that were not in the cloud provider list, so users will see it supports those. But, omitted S3 and webdav, since it's probably better for users to use what's built into git-annex than going via rclone. The rclone list is out of date apparently, as rclone.org has more, so I added a note at the bottom for users to check. This commit was sponsored by Ethan Aubin.
19 lines
869 B
Markdown
19 lines
869 B
Markdown
For using [Google Cloud Storage](https://cloud.google.com/products/cloud-storage)
|
|
as a special remote, there are currently three choices:
|
|
|
|
* Google Cloud Storage supports supports the same API as Amazon S3, so
|
|
git-annex's built-in [[S3 special remote|special_remotes/S3]] can be used
|
|
with it. You may need to configure Google Cloud Storage to allow
|
|
"Interoperable Access". Here is how to set up the special remote:
|
|
|
|
git annex initremote cloud type=S3 encryption=none host=storage.googleapis.com port=80
|
|
|
|
* Alternatively, rclone supports Google Cloud Storage's native API,
|
|
so the [[rclone_special_remote|special_remotes/rclone]] can be used.
|
|
|
|
* Alternatively, there is a dedicated special remote,
|
|
<https://github.com/bgilbert/gcsannex>
|
|
(Last updated 2016)
|
|
|
|
At this time it's not clear which is better, so if you find one works
|
|
best, please comment below.
|