Open Source Continuous File Synchronization
Go to file
Chris Joel ac079f0f83 Implement identicon representation for devices.
The first fifteen characters of device IDs are now used to procedurally
generate psuedo-unique avatars for their respective devices. The avatars
are represented using SVG elements that replace the icons previously
shown next to device names in the GUI.
2014-10-16 12:28:43 -07:00
assets Logo update 2014-08-06 09:07:13 +02:00
cmd Merge pull request #848 from pluby/discovery 2014-10-16 09:11:08 +02:00
Godeps Dependencies 2014-10-16 14:58:11 +02:00
gui Implement identicon representation for devices. 2014-10-16 12:28:43 -07:00
internal Implement identicon representation for devices. 2014-10-16 12:28:43 -07:00
protocol Manual fixup 2014-09-28 14:23:08 +01:00
test Handle .stfolder completely in integration test 2014-10-16 12:12:59 +02:00
.gitignore Do honest test coverage analysis in Jenkins 2014-08-19 12:43:50 +02:00
build.go Don't add newline on version string (fixes #865) 2014-10-15 18:15:40 +02:00
build.sh Silence failing ulimit calls 2014-09-06 15:04:49 +01:00
check-contrib.sh Complete rewrite of the puller (fixes #638, fixes #715, fixes #701) 2014-09-27 21:51:08 +02:00
CONTRIBUTING.md Relicense to GPL 2014-10-01 07:53:59 +02:00
CONTRIBUTORS Add pluby 2014-10-16 09:09:41 +02:00
LICENSE Relicense to GPL 2014-10-01 07:53:59 +02:00
README.md Relicense to GPL 2014-10-01 07:53:59 +02:00

syncthing

Latest Build API Documentation GPL License

This is the syncthing project. The following are the project goals:

  1. Define a protocol for synchronization of a folder between a number of collaborating devices. The protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is the Block Exchange Protocol.

  2. Provide the reference implementation to demonstrate the usability of said protocol. This is the syncthing utility. It is the hope that alternative, compatible implementations of the protocol will come to exist.

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.

Building

Building Syncthing from source is easy, and there's a guide that describes it for both Unix and Windows.

Signed Releases

As of v0.7.0 and onwards, git tags and release binaries are GPG signed with the key BCE524C7 (http://nym.se/gpg.txt). For release binaries, MD5 and SHA1 checksums are calculated and signed, available in the md5sum.txt.asc and sha1sum.txt.asc files.

Documentation

The syncthing documentation is on the discourse site.

License

All documentation and protocol specifications are licensed under the Creative Commons Attribution 4.0 International License.

All code is licensed under the GPL, v3 or later.