-
Notifications
You must be signed in to change notification settings - Fork 9
Usage
I've tried to keep the app self-explanatory yet simple. Nevertheless, here are some random notes on usage.
Profiles are a directory, similar to HOME for Taskwarrior.
Profiles contain a task list (pending, etc), persisted aliased queries of sort and filter selections, and optionally a Taskserver configuration.
The directory name is a UUID, the initial name, and you can rename to an alias.
To set taskd.server and taskd.credentials, press "Select TASKRC"
and add a file that contains those settings.
Once taskd.server is set, if you tap it, it will rename the alias to
name of server.
To set PEM files, press the appropriate button, select the PEM file, and the contents and filename will be stored, and the filename will be diplayed in UI.
The SHA1 fingerprint will only be displayed for certificates, not keys.
To remove a PEM file, long press the setting.
The taskd.ca is found to be optional, for example if you use Let's
Encrypt.
The server.cert on your server will not work on iOS clients if
they're generated with Taskserver project's pki scripts. This is a
known issue not sufficiently researched by me. In this case, you'll be
prompted, the SHA1 fingerprint of the server.cert will be shown, and
you may dismiss, or export the cert to device to inspect, or trust for
further connections. If you press trust, the server.cert will be
displayed in the config screen with SHA1 fingerprint. Tap it to
remove.
Press the graph/statistics button in upper right corner to test your
connection, which sends the type: statistics request to the
Taskserver.
This copies your Taskserver configuration to a new profile.
This is like a copy of your profile, without the tasks or persisted queries.
Here are some usecases:
The sync key in your backlog.data may not work if you changed
something at server's tx.data. With Taskwarrior, a solution might be
task sync init, which if I understand correctly, discards your
backlog.data, circumventing the bad sync key, and resends all data
from pending.data and completed.data.
The command task sync init is not yet implemented in this app, so a
similar solution would be to copy your Taskserver configuration to a
new profile.
Note this discards any changes on device that have not been received
by Taskserver. You may want to use Export tasks to recover these
changes.
You might have a second account that has the same PEM files, but just needs a different TASKRC file. Copy the config to a new profile, and change the TASKRC file before syncing the new profile.
You might want to research a potential bug or issue, or describe steps to reproduce. Copying a Taskserver configuration to a clean profile might assist in this.
This removes the directory with name the UUID mentioned above, which can contain tasks, queries, TASKRC and PEM files.
Queries persist a set of sorts and filters.
They are persisted in a subdirectory of a profile, and implemented as each persisted query is a directory with name a UUID, and you can add an alias.