Which taskserver sync mechanism to build upon?

[a-t-0]

Context

A while ago, I wrote a poor automation of the taskserver installation, such that it syncs with taskwarrior. Now I've automated (somewhat decent) self-signed SSL certificates for https onion domains. I would like to apply these auto-generated SSL certificates to taskserver, to make the self-hosted taskserver (for taskwarrior and timewarrior) run from any place with internet/tor access (within a single command).

Given the wide scope of development (e.g. with taskchampion (related thread), and Task Git Sync etc.), I would like to verify my efforts on automating this self-hosted taskwarrior synchronisation mechanism over tor, are aimed at a non-outdated sync protocol. Therefore, I would like to ask:

Question

Is the current taskserver sync mechanism still the recommended taskserver mechanism, or would it be advisable to look at a different, still-in-development sync mechanism?

[djmitche]

I am working toward dropping support for taskserver and the existing sync functionality in #3094. I can't tell the future, but my hope is that 3.0 will use Taskchampion.

One of the things that needs doing before that time is "productionizing" the taskchampion-sync-server. It's currently not very 12-factor compatible (takes config as command-line arguments) and allows creation of new clients without any other kind of authentication. It'd be great to have some perspective on that, leading to a set of issues to fix. Some of those will require Rust work, but some will be more operational in nature. Are you interested?

[a-t-0]

Thank you for your clear and quick response, and for acquainting me with twelve-factor compatibility. I would love to contribute, and get hands-on with rust, however, I am currently focussed on finishing my studies and finding an income. So if it would be possible to receive some funding for the work, I would be happy to work on "productionizing" the taskchampion-sync-server.

[djmitche]

Sounds great!