|Martchus 3bf9443150||3 years ago|
|.github||7 months ago|
|assets||1 year ago|
|c-bindings||1 week ago|
|cmd||1 week ago|
|etc||1 month ago|
|gui||4 weeks ago|
|lib||1 week ago|
|man||1 month ago|
|meta||1 month ago|
|next-gen-gui||1 month ago|
|proto||1 month ago|
|script||1 month ago|
|test||4 weeks ago|
|.codecov.yml||2 years ago|
|.deepsource.toml||4 weeks ago|
|.gitattributes||4 years ago|
|.gitignore||2 months ago|
|.golangci.yml||1 year ago|
|AUTHORS||1 month ago|
|CONDUCT.md||3 years ago|
|CONTRIBUTING.md||5 years ago|
|Dockerfile||1 month ago|
|Dockerfile.builder||12 months ago|
|Dockerfile.buildx||1 month ago|
|Dockerfile.stdiscosrv||12 months ago|
|Dockerfile.strelaysrv||12 months ago|
|GOALS.md||3 years ago|
|LICENSE||4 years ago|
|README-Docker.md||1 month ago|
|README.md||10 months ago|
|build.go||1 month ago|
|build.ps1||11 months ago|
|build.sh||11 months ago|
|go.mod||1 month ago|
|go.sum||1 month ago|
Syncthing is a continuous file synchronization program. It synchronizes files between two or more computers. We strive to fulfill the goals below. The goals are listed in order of importance, the most important one being the first. This is the summary version of the goal list - for more commentary, see the full Goals document.
Syncthing should be:
Safe From Data Loss
Protecting the user's data is paramount. We take every reasonable precaution to avoid corrupting the user's files.
Secure Against Attackers
Again, protecting the user's data is paramount. Regardless of our other goals we must never allow the user's data to be susceptible to eavesdropping or modification by unauthorized parties.
Easy to Use
Syncthing should be approachable, understandable and inclusive.
User interaction should be required only when absolutely necessary.
Syncthing should run on every common computer. We are mindful that the latest technology is not always available to any given individual.
Syncthing is primarily about empowering the individual user with safe, secure and easy to use file synchronization.
There are many things we care about that don't make it on to the list. It is fine to optimize for these values, as long as they are not in conflict with the stated goals above.
Take a look at the getting started guide.
To run Syncthing in Docker, see the Docker README.
We'd like to encourage you to vote on issues that matter to you. This helps the team understand what are the biggest pain points for our users, and could potentially influence what is being worked on next.
The first and best point of contact is the Forum. There is also an IRC
#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 Syncthing from source is easy, and there's a guide that describes it for both Unix and Windows systems.
As of v0.10.15 and onwards release binaries are GPG signed with the key D26E6ED000654A3E, available from https://syncthing.net/security.html and most key servers.
There is also a built in automatic upgrade mechanism (disabled in some distribution channels) which uses a compiled in ECDSA signature. macOS binaries are also properly code signed.
Please see the Syncthing documentation site.
All code is licensed under the MPLv2 License.