gui, man: Update docs & translations
GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/4320
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "STDISCOSRV" "1" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "STDISCOSRV" "1" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
stdiscosrv \- Syncthing Discovery Server
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "STRELAYSRV" "1" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "STRELAYSRV" "1" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
strelaysrv \- Syncthing Relay Server
|
||||
.
|
||||
@@ -144,6 +144,7 @@ An optional description about who provides the relay.
|
||||
.TP
|
||||
.B \-status\-srv=<listen addr>
|
||||
Listen address for status service (blank to disable) (default ":22070").
|
||||
Status service is used by the relay pool server UI for displaying stats (data transfered, number of clients, etc.)
|
||||
.UNINDENT
|
||||
.SH SETTING UP
|
||||
.sp
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-BEP" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-BEP" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-bep \- Block Exchange Protocol v1
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-CONFIG" "5" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-CONFIG" "5" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-config \- Syncthing Configuration
|
||||
.
|
||||
@@ -655,7 +655,7 @@ slow response time (slow connection/cpu) and large index exchanges.
|
||||
Ping interval in seconds. Don\(aqt change it unless you feel it\(aqs necessary.
|
||||
.TP
|
||||
.B minHomeDiskFree
|
||||
The minimum required free space that should be available on the the
|
||||
The minimum required free space that should be available on the
|
||||
partition holding the configuration and index. Accepted units are \fB%\fP, \fBkB\fP,
|
||||
\fBMB\fP, \fBGB\fP and \fBTB\fP\&.
|
||||
.TP
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-DEVICE-IDS" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-DEVICE-IDS" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-device-ids \- Understanding Device IDs
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-EVENT-API" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-EVENT-API" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-event-api \- Event API
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-FAQ" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-FAQ" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-faq \- Frequently Asked Questions
|
||||
.
|
||||
@@ -424,6 +424,28 @@ Syncthing logs to stdout by default. On Windows Syncthing by default also
|
||||
creates \fBsyncthing.log\fP in Syncthing\(aqs home directory (run \fBsyncthing
|
||||
\-paths\fP to see where that is). Command line option \fB\-logfile\fP can be used
|
||||
to specify a user\-defined logfile.
|
||||
.SS How can I view the history of changes?
|
||||
.sp
|
||||
The web GUI contains a \fBGlobal Changes\fP button under the device list which
|
||||
displays changes since the last (re)start of Syncthing. With the \fB\-audit\fP
|
||||
option you can enable a persistent, detailed log of changes and most
|
||||
activities, which contains a \fBJSON\fP formatted sequence of events in the
|
||||
\fB~/.config/syncthing/audit\-_date_\-_time_.log\fP file.
|
||||
.SS Does the audit log contain every change?
|
||||
.sp
|
||||
The audit log (and the \fBGlobal Changes\fP window) sees the changes that your
|
||||
Syncthing sees. When Syncthing is continuously connected it usually sees every change
|
||||
happening immediately and thus knows which node initiated the change.
|
||||
When topology gets complex or when your node reconnects after some time offline,
|
||||
Syncthing synchronises with its neighbours: It gets the latest synchronised state
|
||||
from the neighbour, which is the \fIresult\fP of all the changes between the last
|
||||
known state (before disconnect or network delay) and the current state at the
|
||||
neighbour, and if there were updates, deletes, creates, conflicts, which were
|
||||
overlapping we only see the \fIlatest change\fP for a given file or directory (and
|
||||
the node where that latest change occurred). When we connect to multiple neighbours
|
||||
Syncthing decides which neighbor has the latest state, or if the states conflict
|
||||
it initiates the conflict resolution procedure, which in the end results in a consistent
|
||||
up\-to\-date state with all the neighbours.
|
||||
.SS How do I upgrade Syncthing?
|
||||
.sp
|
||||
If you use a package manager such as Debian\(aqs apt\-get, you should upgrade
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-GLOBALDISCO" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-GLOBALDISCO" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-globaldisco \- Global Discovery Protocol v3
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-LOCALDISCO" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-LOCALDISCO" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-localdisco \- Local Discovery Protocol v4
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-NETWORKING" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-NETWORKING" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-networking \- Firewall Setup
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-RELAY" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-RELAY" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-relay \- Relay Protocol v1
|
||||
.
|
||||
@@ -99,7 +99,7 @@ which then can be used to establish a connection in session mode.
|
||||
.sp
|
||||
If the client fails to send a JoinRelayRequest message within the first ping
|
||||
interval, the connection is terminated.
|
||||
If the client fails to send a message (even if its a ping message) every minute
|
||||
If the client fails to send a message (even if it\(aqs a ping message) every minute
|
||||
(by default), the connection is terminated.
|
||||
.SS Temporary protocol submode
|
||||
.sp
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-REST-API" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-REST-API" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-rest-api \- REST API
|
||||
.
|
||||
@@ -45,6 +45,49 @@ the configuration file. To use an API key, set the request header
|
||||
"X\-API\-Key: abc123" http://localhost:8384/rest/...\fP can be used to invoke
|
||||
with \fBcurl\fP\&.
|
||||
.SH SYSTEM ENDPOINTS
|
||||
.SS GET /rest/system/browse
|
||||
.sp
|
||||
Returns a list of directories matching the path given by the optional parameter
|
||||
\fBcurrent\fP\&. The path can use \fI\%patterns as described in Go\(aqs filepath package\fP <\fBhttps://golang.org/pkg/path/filepath/#Match\fP>\&. A \(aq*\(aq will always be appended
|
||||
to the given path (e.g. \fB/tmp/\fP matches all its subdirectories). If the option
|
||||
\fBcurrent\fP is not given, filesystem root paths are returned.
|
||||
.INDENT 0.0
|
||||
.INDENT 3.5
|
||||
.sp
|
||||
.nf
|
||||
.ft C
|
||||
$ curl \-H "X\-API\-Key: yourkey" localhost:8384/rest/system/browse | json_pp
|
||||
[
|
||||
"/"
|
||||
]
|
||||
|
||||
$ curl \-H "X\-API\-Key: yourkey" localhost:8384/rest/system/browse?current=/var/ | json_pp
|
||||
[
|
||||
"/var/backups/",
|
||||
"/var/cache/",
|
||||
"/var/lib/",
|
||||
"/var/local/",
|
||||
"/var/lock/",
|
||||
"/var/log/",
|
||||
"/var/mail/",
|
||||
"/var/opt/",
|
||||
"/var/run/",
|
||||
"/var/spool/",
|
||||
"/var/tmp/"
|
||||
]
|
||||
|
||||
$ curl \-H "X\-API\-Key: yourkey" localhost:8384/rest/system/browse?current=/var/*o | json_pp
|
||||
[
|
||||
"/var/local/",
|
||||
"/var/lock/",
|
||||
"/var/log/",
|
||||
"/var/opt/",
|
||||
"/var/spool/"
|
||||
]
|
||||
.ft P
|
||||
.fi
|
||||
.UNINDENT
|
||||
.UNINDENT
|
||||
.SS GET /rest/system/config
|
||||
.sp
|
||||
Returns the current configuration.
|
||||
@@ -407,7 +450,7 @@ Returns the list of recent log entries.
|
||||
.sp
|
||||
Pause the given device or all devices.
|
||||
.sp
|
||||
Takes the optional parameter \fBdevice\fP (device ID). When ommitted,
|
||||
Takes the optional parameter \fBdevice\fP (device ID). When omitted,
|
||||
pauses all devices. Returns status 200 and no content upon success, or status
|
||||
500 and a plain text error on failure.
|
||||
.SS GET /rest/system/ping
|
||||
@@ -451,7 +494,7 @@ Post with empty body to immediately restart Syncthing.
|
||||
.sp
|
||||
Resume the given device or all devices.
|
||||
.sp
|
||||
Takes the optional parameter \fBdevice\fP (device ID). When ommitted,
|
||||
Takes the optional parameter \fBdevice\fP (device ID). When omitted,
|
||||
resumes all devices. Returns status 200 and no content upon success, or status
|
||||
500 and a plain text error on failure.
|
||||
.SS POST /rest/system/shutdown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-SECURITY" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-SECURITY" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-security \- Security Principles
|
||||
.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-STIGNORE" "5" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-STIGNORE" "5" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-stignore \- Prevent files from being synchronized to other nodes
|
||||
.
|
||||
@@ -116,7 +116,8 @@ Windows does not support escaping \fB\e[foo \- bar\e]\fP\&.
|
||||
\fBNOTE:\fP
|
||||
.INDENT 0.0
|
||||
.INDENT 3.5
|
||||
Prefixes can be specified in any order.
|
||||
Prefixes can be specified in any order (e.g. "(?d)(?i)"), but cannot be in a
|
||||
single pair of parentheses (not "(?di)").
|
||||
.UNINDENT
|
||||
.UNINDENT
|
||||
.SH EXAMPLE
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-VERSIONING" "7" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING-VERSIONING" "7" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-versioning \- Keep automatic backups of deleted files by other nodes
|
||||
.
|
||||
@@ -35,8 +35,8 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
|
||||
Syncthing supports archiving the old version of a file when it is deleted or
|
||||
replaced with a newer version from the cluster. This is called "file
|
||||
versioning" and uses one of the available \fIversioning strategies\fP described
|
||||
below. File versioning is configured per folder and defaults to "no file
|
||||
versioning", i.e. no old copies of files are kept.
|
||||
below. File versioning is configured per folder, on a per\-device basis, and
|
||||
defaults to "no file versioning", i.e. no old copies of files are kept.
|
||||
.SH TRASH CAN FILE VERSIONING
|
||||
.sp
|
||||
This versioning strategy emulates the common "trash can" approach. When a file
|
||||
@@ -97,10 +97,17 @@ only for 10 days, use 10. \fBNote: Set to 0 to keep versions forever.\fP
|
||||
.SH EXTERNAL FILE VERSIONING
|
||||
.sp
|
||||
This versioning method delegates the decision on what to do to an external
|
||||
command (program or script). The only configuration option is the name of the
|
||||
command. This should be an absolute path name. Just prior to a file being
|
||||
replaced, the command will be run with two parameters: the path to the folder,
|
||||
and the path to the file within the folder.
|
||||
command (program or script).
|
||||
Just prior to a file being replaced, the command will be run.
|
||||
The command should be specified as an absolute path, and can use the following templated arguments:
|
||||
.INDENT 0.0
|
||||
.TP
|
||||
.B %FOLDER_PATH%
|
||||
Path to the folder
|
||||
.TP
|
||||
.B %FILE_PATH%
|
||||
Path to the file within the folder
|
||||
.UNINDENT
|
||||
.SS Example for Unixes
|
||||
.sp
|
||||
Lets say I want to keep the latest version of each file as they are replaced
|
||||
@@ -133,8 +140,7 @@ mv \-f "$folderpath/$filepath" "$versionspath/$filepath"
|
||||
.UNINDENT
|
||||
.sp
|
||||
I must ensure that the script has execute permissions (\fBchmod 755
|
||||
onlylatest.sh\fP), then configure Syncthing with the above path as the command
|
||||
name.
|
||||
onlylatest.sh\fP), then configure Syncthing with command \fB/Users/jb/bin/onlylatest.sh %FOLDER_PATH% %FILE_PATH%\fP
|
||||
.sp
|
||||
Lets assume I have a folder "default" in ~/Sync, and that within that folder
|
||||
there is a file \fBdocs/letter.txt\fP that is being replaced or deleted. The
|
||||
@@ -186,7 +192,7 @@ move /Y "%FOLDER_PATH%\e%FILE_PATH%" "%VERSIONS_PATH%\e%FILE_PATH%"
|
||||
.UNINDENT
|
||||
.UNINDENT
|
||||
.sp
|
||||
Finally, I set \fBC:\eUsers\emfrnd\eScripts\eonlylatest.bat\fP as command name in
|
||||
Finally, I set \fBC:\eUsers\emfrnd\eScripts\eonlylatest.bat %FOLDER_PATH% %FILE_PATH%\fP as command name in
|
||||
Syncthing.
|
||||
.SH AUTHOR
|
||||
The Syncthing Authors
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING" "1" "July 03, 2017" "v0.14" "Syncthing"
|
||||
.TH "SYNCTHING" "1" "August 19, 2017" "v0.14" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing \- Syncthing
|
||||
.
|
||||
|
||||
Reference in New Issue
Block a user