Open Source Continuous File Synchronization
Go to file
2016-01-03 19:59:56 +01:00
assets Add .gitattributes; normalize line endings 2015-04-25 23:16:46 +09:00
cmd Ignore error on os.Chtimes in config archiving 2015-12-26 18:25:36 +01:00
etc systemd: Remove exit code 2, due to #2578 2015-12-15 08:38:08 +01:00
Godeps Update kardianos/osext (fixes #2650) 2016-01-03 19:59:56 +01:00
gui Update docs & translations 2016-01-03 09:56:33 +01:00
lib Update docs & translations 2016-01-03 09:56:33 +01:00
man Update docs & translations 2016-01-03 09:56:33 +01:00
protocol The protocol specs moved again 2015-01-09 08:54:19 +01:00
script White list commit e37cef 2015-11-16 20:48:40 +01:00
test Generate ECDSA keys instead of RSA 2015-11-27 09:15:12 +01:00
.gitattributes Revert "Enforce line endings when cloning (fixes #1766)" 2015-05-07 22:55:31 +02:00
.gitignore Revert "Merge pull request #2440 from Stefan-Code/master" 2015-11-09 14:23:26 +01:00
.mailmap Include ref#, show author nickname in release notes 2014-12-07 12:52:18 +01:00
appveyor.yaml Add AppVeyor for Windows builds 2015-09-20 15:18:50 +02:00
AUTHORS Add ironmig 2015-12-30 08:53:19 +01:00
build.go Also build linux-arm64, linux-ppc64, linux-ppc64le 2016-01-01 20:56:31 +01:00
build.sh Also build linux-arm64, linux-ppc64, linux-ppc64le 2016-01-01 20:56:31 +01:00
CONDUCT.md Add Code of Conduct 2014-12-02 15:57:31 +01:00
CONTRIBUTING.md Links are nice, too 2015-06-10 00:04:53 +02:00
LICENSE MPLv2 2015-03-17 16:02:27 +01:00
NICKS Add ironmig 2015-12-30 08:53:19 +01:00
README.md Clarify points of contact 2016-01-03 13:07:22 +01:00

Syncthing

Latest Build (Official) AppVeyor Build API Documentation MPLv2 License

This is the Syncthing project which pursues the following goals:

  1. 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.

  2. Provide the reference implementation to demonstrate the usability of said protocol. This is the syncthing utility. 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.

Getting in Touch

The first and best point of contact is the Forum. There is also an IRC channel, #syncthing on Freenode (with a web client), for talking directly to developers and users. If you've found something that is clearly a bug, feel free to report it in the GitHub issue tracker.

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.