go/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2025-08-10 06:09:44 +02:00
Code Issues Releases Activity

filescom: document that hashes need to be enabled - fixes #8674

Browse Source
This commit is contained in:
Nick Craig-Wood
2025-07-11 14:14:18 +01:00
parent f3f16cd2b9
commit bfdd5e2c22
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/content/filescom.md
View File

@@ -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