"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Go azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
filescom: document that hashes need to be enabled - fixes #8674
Nick Craig-Woodbfdd5e2c2263
diff --git a/docs/content/filescom.md b/docs/content/filescom.mdindex 2a718a7a5..95acf3339 100644--- a/docs/content/filescom.md+++ b/docs/content/filescom.md@@ -99,6 +99,21 @@ excess files in the directory.rclone sync --interactive /home/local/directory remote:dir+### Hashes++In December 2024 `files.com` started [supporting more checksums](https://www.files.com/blog/2024/11/01/new-modern-checksum-options-now-available-with-opt).++However if you want hashes you **must** enable them in your site by+visiting the "File Integrity" section in "Data Governance" to+configure your settings and select the checksum algorithms that meet+your requirements.++Rclone currently only support CRC32 and MD5 for use in syncing but+selecting more checksums will not affect rclone's operations.++For use with rclone, selecting at least MD5 is recommended so rclone+can do an end to end integrity check.+{{< rem autogenerated options start" - DO NOT EDIT - instead edit fs.RegInfo in backend/filescom/filescom.go then run make backenddocs" >}}### Standard options