gergely/taskwarrior-2.x
1
0
Fork 0
Code Issues Actions Packages Projects Releases 1 Wiki Activity

TW-1474: Documentation is confusing with respect to user/uuid on the server

Browse Source 
- Man page clarified, mention of 'password' removed (thanks to Tomas Babej).
This commit is contained in:
Paul Beckingham
2015-05-03 11:21:01 -04:00
parent b6b49ca7e4
commit c8756f0201
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog
View File

@@ -1,5 +1,7 @@
2.4.4 () - 2.4.4 () -
- TW-1474 Documentation is confusing with respect to user/uuid on the server
(thanks to Tomas Babej).
- TW-1596 taskwarrior can't compile FreeBSD 9.3 32bit environment (thanks to - TW-1596 taskwarrior can't compile FreeBSD 9.3 32bit environment (thanks to
ribbon) ribbon)
- TW-1603 Priority color precedence changed since it is a UDA, should be lowered - TW-1603 Priority color precedence changed since it is a UDA, should be lowered

13
doc/man/task-sync.5.in
View File

@@ -80,24 +80,25 @@ The Taskserver was designed for this purpose to be secure, fast and conflict
free, allowing data interchange between assorted Taskwarrior clients, and free, allowing data interchange between assorted Taskwarrior clients, and
tolerant of network connectivity problems. tolerant of network connectivity problems.
There is a 'sync' command built in to Taskwarrior, and with a server account There is a 'sync' command built in to Taskwarrior (provided the GnuTLS library
and client configuration, syncing is done on demand. is installed), and with a server account and client configuration, syncing is
done on demand.
Setup is a matter of creating an account on a Taskserver (see your Taskserver Setup is a matter of creating an account on a Taskserver (see your Taskserver
provider or operate your own - see provider or operate your own - see
http://taskwarrior.org/docs/server_setup.html) http://taskwarrior.org/docs/server_setup.html)
Once you have an account, you'll receive a certificate, key and a password. Once you have an account, you'll receive a certificate, key, and credentials.
You'll need to put the certificate and key somewhere like this: You'll need to put the certificate and key somewhere like this:
$ cp <name>.cert.pem ~/.task $ cp <name>.cert.pem ~/.task
$ cp <name>.key.pem ~/.task $ cp <name>.key.pem ~/.task
Then you configure Taskwarrior, using the account details: Then you configure Taskwarrior, using the provided details:
$ task config taskd.certificate ~/.task/<name>.cert.pem $ task config taskd.certificate ~/.task/<name>.cert.pem
$ task config taskd.key ~/.task/<name>.key.pem $ task config taskd.key ~/.task/<name>.key.pem
$ task config taskd.credentials <organization>/<name>/<password> $ task config taskd.credentials <organization>/<name>/<UUID>
$ task config taskd.server <server domain>:<port> $ task config taskd.server <server domain>:<port>
If you are using a private server, you are likely also using a self-signed If you are using a private server, you are likely also using a self-signed
@@ -108,7 +109,7 @@ certificate, which means you will need one of the following additional entries:
The CA (Certificate Authority) will be used to verify the server certificate. The CA (Certificate Authority) will be used to verify the server certificate.
Alternatively, you can override the cert verification process using: Alternatively, you can override the cert verification process using:
$ task config taskd.trust yes $ task config taskd.trust 'allow all'
This is an insecure option that should be used with caution, because it directs This is an insecure option that should be used with caution, because it directs
Taskwarrior to trust any certificate. Taskwarrior to trust any certificate.