This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
syncthing [2020/03/18 16:33] sdbs [Semi-public Syncthing folders] |
syncthing [2020/10/04 12:26] (current) sdbs [External HDDs] add link |
||
---|---|---|---|
Line 17: | Line 17: | ||
Its //primary// use-case is when a single person has more computers, and wants to keep some folders synchronized on all of them. | Its //primary// use-case is when a single person has more computers, and wants to keep some folders synchronized on all of them. | ||
- | What we use it for, however, is general data sharing - there' | + | === /-\ use-case === |
+ | What we use it for, however, is general data sharing - there' | ||
+ | **WARNING: Because Syncthing wasn't really meant for this sort of use, it requires a bit of carefulness on part of everyone involved. There' | ||
===== How? ===== | ===== How? ===== | ||
- | FIXME | + | |
https:// | https:// | ||
- | === Moving syncthing folders? === | + | |
===== Advanced stuff ===== | ===== Advanced stuff ===== | ||
- | ==== Introducer Mode ==== | ||
- | |||
- | FIXME | ||
==== Send / Receive Only ==== | ==== Send / Receive Only ==== | ||
- | Send / Receive Only are setting | + | Send Only & Receive Only limit the folder/file changes either received or sent from the current machine. |
=== Send Only Folder === | === Send Only Folder === | ||
- All changes from other devices in the cluster are ignored. | - All changes from other devices in the cluster are ignored. | ||
- | | + | |
- Good as master for backups. | - Good as master for backups. | ||
=== Receive Only Folder === | === Receive Only Folder === | ||
- | - Local changes are not distributed | + | - Local changes are not sent to other devices. |
- Good as slave for backups. | - Good as slave for backups. | ||
==== Versioning ==== | ==== Versioning ==== | ||
- | FIXME | + | The default behavior is that Syncthing keeps no history of synced files. |
+ | This is generally what you want, as it saves space on your machine, but it can cause data loss, in case someone else accidentally deletes/ | ||
+ | |||
+ | Syncthing, in typical unix neckbeard fashion, has several different modes of file versioning: | ||
+ | |||
+ | === Trash Can File Versioning === | ||
+ | > This versioning strategy emulates the common “trash can” approach. When a file is deleted or replaced due to a change on a remote device, it is a moved to the trash can in the '' | ||
+ | > A configuration option is available to clean the trash can from files older than a specified number of days. | ||
+ | |||
+ | === Simple File Versioning === | ||
+ | |||
+ | >With “Simple File Versioning” files are moved to the '' | ||
+ | |||
+ | === Other modes and more detailed info === | ||
+ | |||
+ | https:// | ||
==== External HDDs ==== | ==== External HDDs ==== | ||
You can use syncthing with external harddrives. That is good for backup clusters, huge projects, etc. | You can use syncthing with external harddrives. That is good for backup clusters, huge projects, etc. | ||
On windows it helps to set fixed drive letter to your hardrive, so there are no mismatches. | On windows it helps to set fixed drive letter to your hardrive, so there are no mismatches. | ||
+ | |||
+ | |||
>When assigning your drive letter, make sure to choose a letter toward the end of the alphabet list. For example, X, Y, or Z — otherwise Windows has the tendency to eventually assign a different letter. Also, keep in mind that it will only be the assigned letter on the computer you changed it on. If you take your external drive to a different PC, Windows will give it a different dynamic letter.((From https:// | >When assigning your drive letter, make sure to choose a letter toward the end of the alphabet list. For example, X, Y, or Z — otherwise Windows has the tendency to eventually assign a different letter. Also, keep in mind that it will only be the assigned letter on the computer you changed it on. If you take your external drive to a different PC, Windows will give it a different dynamic letter.((From https:// | ||
+ | https:// | ||
+ | ===== QnA ===== | ||
+ | |||
+ | ==== Common Gotchas ==== | ||
+ | |||
+ | === folder marker missing // .stfolder blues === | ||
+ | |||
+ | Syncthing marks each synced folder with an empty, hidden directory in that folder, called '' | ||
+ | |||
+ | If that (empty) folder is deleted, Syncthing will vomit with a similar error message: | ||
+ | |||
+ | 2020-04-02 21:12:50: Error on folder " | ||
+ | |||
+ | This can happen for a couple of reasons: | ||
+ | |||
+ | * Actual potential data loss - you should [[S.M.A.R.T.|check your disks]] and remember where you keep your backups. | ||
+ | * Some sort of "empty folder cleanup" | ||
+ | * If that's the case, and it's really the only thing that happened, it's safe to simply re-create '' | ||
+ | * If not, and you still do this, you've just successfully corrupted everyone else's Syncthing folders with your broken data. | ||
+ | * Entire folder is missing. See [[syncthing# | ||
+ | ==== CPU ==== | ||
+ | |||
+ | > | ||
+ | |||
+ | >To minimize the impact of this, Syncthing attempts to lower the process priority when starting up. | ||
+ | |||
+ | >To further limit the amount of CPU used when syncing and scanning, set the environment variable GOMAXPROCS to the maximum number of CPU cores Syncthing should use at any given moment. For example, GOMAXPROCS=2 on a machine with four cores will limit Syncthing to no more than half the system’s CPU power. | ||
+ | |||
+ | ==== Whitelisting files ==== | ||
+ | |||
+ | FIXME | ||
+ | ==== Moving syncthing folders? ==== | ||
+ | |||
+ | FIXME | ||
===== Semi-public Syncthing folders ===== | ===== Semi-public Syncthing folders ===== | ||
See [[internal: | See [[internal: |