TaskChampion is the task database Taskwarrior uses to store and sync tasks. This repository implements a sync server against which Taskwarrior and other applications embedding TaskChampion can sync.
This repository was spun off from Taskwarrior itself after the 3.0.0 release. It is still under development and currently best described as a reference implementation of the Taskchampion sync protocol.
It is comprised of three crates:
taskchampion-sync-server-core
implements the core of the protocoltaskchmpaion-sync-server-sqlite
implements an SQLite backend for the coretaskchampion-sync-server
implements a simple HTTP server for the protocol
The server is a simple binary that serves HTTP requests on a TCP port. The server does not implement TLS; for public deployments, the recommendation is to use a reverse proxy such as Nginx, haproxy, or Apache httpd.
Every release of the server generates a Docker image in
ghcr.io/gothenburgbitfactory/taskchampion-sync-server
. The tags include
latest
for the latest release, and both minor and patch versions, e.g., 0.5
and 0.5.1
.
The docker-compose.yml
file in this repository is
sufficient to run taskchampion-sync-server, including setting up TLS
certificates using Lets Encrypt, thanks to Caddy.
You will need a server with ports 80 and 443 open to the Internet and with a fixed, publicly-resolvable hostname. These ports must be available both to your Taskwarrior clients and to the Lets Encrypt servers.
On that server, clone this repository (or just download docker-compose.yml
to
the current directory -- the rest of the contents of this repository are not
required) and run
TASKCHAMPION_SYNC_SERVER_HOSTNAME=taskwarrior.example.com docker compose up
It can take a few minutes to obtain the certificate; the caddy container will
log a message "certificate obtained successfully" when this is complete, or
error messages if the process fails. Once this process is complete, configure
your .taskrc
's to point to the server:
sync.server.url=https://taskwarrior.example.com
sync.server.client_id=[your client-id]
sync.encryption_secret=[your encryption secret]
The docker-compose images store data in a docker volume named
taskchampion-sync-server_data
. This volume contains all of the task data, as
well as the TLS certificate information. It will persist over restarts, in a
typical Docker installation. The docker containers will start automatically on
system startup. See the docker-compose documentation for more information.
The server is configured with command-line options. See
taskchampion-sync-server --help
for full details.
The --data-dir
option specifies where the server should store its data, and
--port
gives the port on which the HTTP server runs.
By default, the server allows all client IDs. To limit the accepted client IDs,
such as when running a personal server, use --allow-client-id <client-id>
.
The server only logs errors by default. To add additional logging output, set
environment variable RUST_LOG
to info
to get a log message for every
request, or to debug
to get more verbose debugging output.
TaskChampion Sync-Server build has been tested with current Rust stable
release version. You can install Rust from your distribution package or use
rustup
.
rustup default stable
If you prefer, you can use the stable version only for install TaskChampion Sync-Server (you must clone the repository first).
rustup override set stable
To build TaskChampion Sync-Server binary simply execute the following commands.
git clone https://github.com/GothenburgBitFactory/taskchampion-sync-server.git
cd taskchampion-sync-server
cargo build --release
After build the binary is located in
target/release/taskchampion-sync-server
.
To build the container execute the following commands.
source .env
docker build \
--build-arg RUST_VERSION=${RUST_VERSION} \
--build-arg ALPINE_VERSION=${ALPINE_VERSION} \
-t taskchampion-sync-server .
Now to run it, simply exec.
docker run -t -d \
--name=taskchampion \
-p 8080:8080 \
taskchampion-sync-server
This start TaskChampion Sync-Server and publish the port to host. Please note that this is a basic run, all data will be destroyed after stop and delete container.