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

rename CLI to ta

Browse source
This commit is contained in:
Dustin J. Mitchell 2021-05-01 14:07:00 -04:00
parent 73ad035bed
commit 0f0f2b0e75
13 changed files with 38 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/src/task-sync.md
View file

@ -4,7 +4,7 @@ A single TaskChampion task database is known as a "replica".
A replica "synchronizes" its local information with other replicas via a sync server.
Many replicas can thus share the same task history.
This operation is triggered by running `task sync`.
This operation is triggered by running `ta sync`.
Typically this runs frequently in a cron task.
Synchronization is quick, especially if no changes have occurred.
@ -14,10 +14,10 @@ Without periodic syncs, the storage space used for the task database will grow q
By default, TaskChampion syncs to a "local server", as specified by the `server_dir` configuration parameter.
Every replica sharing a task history should have precisely the same configuration for `server_origin`, `server_client_key`, and `encryption_secret`.
Synchronizing a new replica to an existing task history is easy: begin with an empty replica, configured for the remote server, and run `task sync`.
Synchronizing a new replica to an existing task history is easy: begin with an empty replica, configured for the remote server, and run `ta sync`.
The replica will download the entire task history.
It is possible to switch a single replica to a remote server by simply configuring for the remote server and running `task sync`.
It is possible to switch a single replica to a remote server by simply configuring for the remote server and running `ta sync`.
The replica will upload the entire task history to the server.
Once this is complete, additional replicas can be configured with the same settings in order to share the task history.