61a182077f
This fixes a corner case I discovered in the symlink branch, where we unexpectedly succeed in "replacing" an entire non-empty directory tree with a file or symlink. This happens when archiving is in use, as we then just move the entire tree away into the archive. This is wrong as we should just archive files and fail on non-empty dirs in all cases. New handling first checks what the (old) thing is, and if it's a directory or symlink just does the delete, otherwise does conflict handling or archiving as appropriate. |
||
|---|---|---|
| assets | ||
| cmd | ||
| etc | ||
| Godeps | ||
| gui | ||
| lib | ||
| man | ||
| protocol | ||
| script | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| build.go | ||
| build.sh | ||
| CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| NICKS | ||
| README.md | ||
Syncthing
This is the Syncthing project which pursues the following goals:
-
Define a protocol for synchronization of a folder between a number of collaborating devices. This protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is called the Block Exchange Protocol.
-
Provide the reference implementation to demonstrate the usability of said protocol. This is the
syncthingutility. We hope that alternative, compatible implementations of the protocol will arise.
The two are evolving together; the protocol is not to be considered stable until Syncthing 1.0 is released, at which point it is locked down for incompatible changes.
Getting Started
Take a look at the getting started guide.
There are a few examples for keeping Syncthing running in the background on your system in the etc directory.
There is an IRC channel, #syncthing on Freenode, for talking directly
to developers and users.
Building
Building Syncthing from source is easy, and there's a guide. that describes it for both Unix and Windows systems.
Signed Releases
As of v0.10.15 and onwards, git tags and release binaries are GPG signed with the key D26E6ED000654A3E (see https://syncthing.net/security.html). For release binaries, MD5 and SHA1 checksums are calculated and signed, available in the md5sum.txt.asc and sha1sum.txt.asc files.
Documentation
Please see the Syncthing documentation site.
All code is licensed under the MPLv2 License.