On the bottom of each page, there is an âEdit on Githubâ link. It takes you to the online editing experience for the respective source file and allows you to make a PR (yes, pull request) with the entered changes.
Forking the GitHub - syncthing/docs: Documentation site repo, editing locally, pushing to your fork and then creating a Pull Request from that fork back to the upstream repo would be the more traditional way.
Hi!
Itâd be great if we can have a way to install Syncthing via built-in package manager called winget. Now itâs possible to add a software there to pretty much every developer. Hope you consider adding yours
Great job man, I was working for that with powershell and it was a nightmare (languages, yet installed? / config-dir found ? / set default path for new folders in %userprofile% or elsewhere⊠I guess Iâll try your own soon.
The deviceâs ECDSA public and private key. These form the basis for the device ID. The key must be kept private.
https-cert.pem, https-key.pem
The certificate and key for HTTPS GUI connections. These may be replaced with a custom certificate for HTTPS as desired.
csrftokens.txt
A list of recently issued CSRF tokens (for protection against browser cross site request forgery).
The database is stored either in the same directory as the config (usually the default), but may also be located in one of the following directories (Unix-like platforms only):
If a database exists in the old default location, that location is still used.
If $XDG_DATA_HOME is set, use $XDG_DATA_HOME/syncthing.
If ~/.local/share/syncthing exists, use that location.