BartyDeCanter

Like all projects, you should think about needs, budget, and time. You’ve got a good list of what you want to run which is a good start. Budget is next, particularly considering the price of hardware these days.

FWIW, I run Jellyfin, Navidrome, the entire arr stack, Forgejo, Paperless, mealio, and Immich on a NAS with 24GB RAM and have never needed more. 8GB would have been a bit tight but probably doable. 16 will be plenty for you.

From TFA, emphasis mine:

What veans is for#

Coding agents keep their own to-do lists. Claude Code has TodoWrite, other tools have their own scratch files, and either way that list lives inside a single session and disappears when the session ends. You can’t see it while the agent is working, your teammates can’t see it at all, and nothing survives to the next session.

veans replaces that ephemeral list with real tasks in a Vikunja project. The agent claims a task before it starts, moves it along as it works, and leaves it in review when it’s done. The result is that the agent’s work is visible in the same place you already track everything else: you can watch a task move across the board in real time, comment on it, reprioritize it, or pick up where the agent left off. When the session ends, the trail is still there.

veans itself is built for machines, not people . Everything prints JSON, so it’s made to be consumed by an agent or a script. The human side of the workflow happens in Vikunja.

What Taskwarrior lets you do is something like this for people:

task add priority:high due:thursday depends:32 something I need to do  
task ready   # shows all of my tasks that aren't waiting on something or depending on something  
task project:home-repairs export > home-repairs.json # export my entire home repair project to a json file to process into a gantt chart, budget (since I can add a price tag to each task) and whatever else  

but then I can also have a script that looks like:

# taskfile.sh  
infile="$1"  
proj ="$2"  

while IFS= read -r line; do  
    [ -z "$line" ] && continue  
    [[ "$line" =~ ^[[:space:]]*# ]] && continue  
    echo "Adding task: $line"  
    if [ -n "$proj" ]; then  
        task add "$line" "$proj"  
    else  
        task add "$line"  
    fi  
done < "$input_file"  

which lets me have preset task lists for various things, like:

taskfile.sh ~/tasks/packing-list.txt proj:work-trip  
taskfile.sh ~/tasks/xmas-list.txt proj:xmas-presents  

Thats an administration cli, not a daily use cli.

And, I mean things like being able to take tasks, pipe them through whatever tooling you like, pipe them back in, sync them from any other task system, etc. TaskWarrior has a fully customizable priority and urgency system, tagging, dependency management, and status system. I also like that TaskWarrior is usable completely offline and then can be resynced whenever you feel like it.

Vikunja is great and probably the right choice for most people. But if you do significant project planning for yourself AND want to be able to deal with you todo list programmatically, the only other thing close is orgmode.

Fair enough! The lack of a cli is the deal breaker for Vikunja for me.

There is a WASM ticket being worked on that once it is completed will allow for all sorts of fancy web UIs for TaskWarrior as standalone PWAs or whatever. I should check in on how that’s going.

I’ve taken a brief look at it. The ui is fairly slick, but you have to use it their way and it doesn’t have a cli. How much that matters is up to you.

Instead of new and exciting, how about old and boring? https://taskwarrior.org/
Sync server is self hosted, it’s more configurable and programmable than anything else and has a variety of front ends on different platforms.

And give up the best weather and access to 5 star restaurants in the world? Surely you jest!

Stages of POSIX enlightenment:

1. It couldn’t possibly all be files
2. It’s all files
3. What is a file, anyway?
4. There’s no such thing as a file
5. It couldn’t possibly all be files
6. Everything is a file

Most people stop at stage 2, stage 3 hits when you decide to write a filesystem, stage 4 when you’ve finished your first filesystem. Stage 5 is when you start working on kernel internals. No one can tell you how to reach stage 6, you must discover it for yourself.