mirror of
https://github.com/octoleo/syncthing.git
synced 2024-11-13 00:36:28 +00:00
916ec63af6
This is a new revision of the discovery server. Relevant changes and non-changes: - Protocol towards clients is unchanged. - Recommended large scale design is still to be deployed nehind nginx (I tested, and it's still a lot faster at terminating TLS). - Database backend is leveldb again, only. It scales enough, is easy to setup, and we don't need any backend to take care of. - Server supports replication. This is a simple TCP channel - protect it with a firewall when deploying over the internet. (We deploy this within the same datacenter, and with firewall.) Any incoming client announces are sent over the replication channel(s) to other peer discosrvs. Incoming replication changes are applied to the database as if they came from clients, but without the TLS/certificate overhead. - Metrics are exposed using the prometheus library, when enabled. - The database values and replication protocol is protobuf, because JSON was quite CPU intensive when I tried that and benchmarked it. - The "Retry-After" value for failed lookups gets slowly increased from a default of 120 seconds, by 5 seconds for each failed lookup, independently by each discosrv. This lowers the query load over time for clients that are never seen. The Retry-After maxes out at 3600 after a couple of weeks of this increase. The number of failed lookups is stored in the database, now and then (avoiding making each lookup a database put). All in all this means clients can be pointed towards a cluster using just multiple A / AAAA records to gain both load sharing and redundancy (if one is down, clients will talk to the remaining ones). GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/4648
28 lines
1.1 KiB
Go
28 lines
1.1 KiB
Go
/*
|
|
Package toml provides facilities for decoding and encoding TOML configuration
|
|
files via reflection. There is also support for delaying decoding with
|
|
the Primitive type, and querying the set of keys in a TOML document with the
|
|
MetaData type.
|
|
|
|
The specification implemented: https://github.com/toml-lang/toml
|
|
|
|
The sub-command github.com/BurntSushi/toml/cmd/tomlv can be used to verify
|
|
whether a file is a valid TOML document. It can also be used to print the
|
|
type of each key in a TOML document.
|
|
|
|
Testing
|
|
|
|
There are two important types of tests used for this package. The first is
|
|
contained inside '*_test.go' files and uses the standard Go unit testing
|
|
framework. These tests are primarily devoted to holistically testing the
|
|
decoder and encoder.
|
|
|
|
The second type of testing is used to verify the implementation's adherence
|
|
to the TOML specification. These tests have been factored into their own
|
|
project: https://github.com/BurntSushi/toml-test
|
|
|
|
The reason the tests are in a separate project is so that they can be used by
|
|
any implementation of TOML. Namely, it is language agnostic.
|
|
*/
|
|
package toml
|