Open Source Continuous File Synchronization
Go to file
2015-07-21 20:39:19 +02:00
assets Add .gitattributes; normalize line endings 2015-04-25 23:16:46 +09:00
cmd Make sure CPU profile actually gets written before exiting 2015-07-20 15:34:40 +02:00
etc launchd: Log to files 2015-07-06 21:45:49 +02:00
Godeps Determine conflict winner based on change type and modification time (fixes #1848) 2015-07-21 15:39:20 +02:00
gui Squashed commit of pull request #1981 2015-07-20 14:48:03 +02:00
internal Optionally ignore remote deletes (fixes #1254) 2015-07-21 20:39:19 +02:00
man Translation & docs update 2015-07-19 13:34:11 +02:00
protocol The protocol specs moved again 2015-01-09 08:54:19 +01:00
test Determine conflict winner based on change type and modification time (fixes #1848) 2015-07-21 15:39:20 +02:00
.gitattributes Revert "Enforce line endings when cloning (fixes #1766)" 2015-05-07 22:55:31 +02:00
.gitignore hax 2015-05-11 18:39:53 +02:00
.mailmap Include ref#, show author nickname in release notes 2014-12-07 12:52:18 +01:00
AUTHORS Add dva 2015-07-20 14:25:07 +02:00
authors.go Auto generate author list in gui/index.html 2015-04-04 10:09:42 +02:00
benchfilter.go Run benchmarks when running tests 2015-05-23 15:08:17 +02:00
build.go Squashed commit of pull request #1875 2015-07-20 14:18:07 +02:00
build.sh Squashed commit of pull request #1875 2015-07-20 14:18:07 +02:00
changelog.go changelog.go should not be built 2015-04-20 14:03:50 +09:00
check-contrib.sh Merge remote-tracking branch 'syncthing/pr/1911' 2015-06-03 19:24:30 +02: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 dva 2015-07-20 14:25:07 +02:00
README.md Correct docs site link 2015-06-11 14:24:39 +02:00

Syncthing

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

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.