Open Source Continuous File Synchronization
Go to file
Stefan Tatschner 0580b10385 Cleanup markdown inline link mess
I just wanted to add the freenode webchat link, because people who are
not used to irc can join the chatroom instantly. I tried to clean up the
markdown file a bit and removed the links to the footer; that makes the
"source code" less ugly.
2015-09-26 16:42:15 +02:00
assets Add .gitattributes; normalize line endings 2015-04-25 23:16:46 +09:00
cmd Decouple connections service from model 2015-09-25 12:19:30 -04:00
etc Pull syncthing-inotify.service as an optional dep 2015-09-25 23:39:03 +02:00
Godeps Clean up deps 2015-09-22 19:39:07 +02:00
gui Add burkemw3 2015-09-26 13:15:25 +02:00
lib Clean up connection.Model interface a little 2015-09-26 13:19:22 +02:00
man Translation & docs update 2015-08-30 14:38:47 +02:00
protocol The protocol specs moved again 2015-01-09 08:54:19 +01:00
script Add specific build setup for CircleCI 2015-09-02 14:56:16 +02:00
test Relax folder label restrictions 2015-09-25 13:45:58 +02:00
.gitattributes Revert "Enforce line endings when cloning (fixes #1766)" 2015-05-07 22:55:31 +02:00
.gitignore Remove leftovers from signing 2015-08-31 17:46:48 +02: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 burkemw3 2015-09-26 13:15:25 +02:00
build.go Relax folder label restrictions 2015-09-25 13:45:58 +02:00
build.sh Signing is done by stsigtool only 2015-08-30 20:50:07 +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 burkemw3 2015-09-26 13:15:25 +02:00
README.md Cleanup markdown inline link mess 2015-09-26 16:42:15 +02: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.

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.