GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-06-26 10:54:26 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Documentation

Browse source 
- Now uses proper name 'Taskserver'.
This commit is contained in:
Paul Beckingham 2013-11-16 16:06:23 -05:00
parent 0df30a5be0
commit 6bc352f713
13 changed files with 57 additions and 57 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/man/task-faq.5.in
View file

@ -179,7 +179,7 @@ an alias in the .bashrc file along the lines of
.TP
.B Q: I don't want to use dropbox. Is there another way to synchronize my tasks?
Yes. Get a Task Server account, and sync tasks between all your machines and
Yes. Get a Taskserver account, and sync tasks between all your machines and
devices. See task-sync(5).
.TP

8
doc/man/task-sync.5.in
View file

@ -16,7 +16,7 @@ There are three alternatives for syncing data, which are:
.br
2) File hosting systems, such as DropBox
.br
3) Using the Task Server and the 'sync' command
3) Using the Taskserver and the 'sync' command
.SH OPTION 1: VERSION CONTROL SYSTEMS
@ -75,15 +75,15 @@ Weaknesses:
- Tasks are not properly merged
.SH OPTION 3: TASK SERVER
The Task Server was designed for this purpose to be secure, fast and conflict
.SH OPTION 3: TASKSERVER
The Taskserver was designed for this purpose to be secure, fast and conflict
free, allowing data interchange between assorted Taskwarrior clients, and
tolerant of network connectivity problems.
There is a 'sync' command built in to Taskwarrior, and with a server account
and client configuration, syncing is done on demand.
Setup is a matter of creating an account on a Task Server (see your Task Server
Setup is a matter of creating an account on a Taskserver (see your Taskserver
provider or operate your own - see
http://taskwarrior.org/projects/taskwarrior/wiki/Server_setup)

12
doc/man/taskrc.5.in
View file

@ -1341,41 +1341,41 @@ server.
.TP
.B taskd.server=<host>:<port>
.RS
Specifies the hostname and port of the task server. Hostname may be an IPv4 or
Specifies the hostname and port of the Taskserver. Hostname may be an IPv4 or
IPv6 address, or domain. Port is an integer.
.RE
.TP
.B taskd.credentials=<organization>/<user>/<key>
.RS
User identification for the task server, which includes a private key.
User identification for the Taskserver, which includes a private key.
.RE
.TP
.B taskd.certificate=<path>
.RS
Specifies the path to the client certificate used for identification with the
task server.
Taskserver.
.RE
.TP
.B taskd.key=<path>
.RS
Specifies the path to the client key used for encrypted communication with the
task server.
Taskserver.
.RE
.TP
.B taskd.ca=<path>
.RS
Specifies the path to the CA certificate in the event that your task server is
Specifies the path to the CA certificate in the event that your Taskserver is
using a self-signed certificate. Optional.
.RE
.TP
.B taskd.trust=yes|no
.RS
If you do not specify a CA certificate when your task server is using a self-
If you do not specify a CA certificate when your Taskserver is using a self-
signed certificate, you can override the certificate validation by setting this
value to 'yes'. Default is not to trust a server certificate.
.RE

2
doc/misc/tutorial/extra.txt
View file

@ -5,7 +5,7 @@ Calendar trick
Metadata
Sync
sync (needs 2.3.0 & task server)
sync (needs 2.3.0 & Taskserver)
Logo?