• 0 Posts
  • 127 Comments
Joined 5 months ago
cake
Cake day: May 2nd, 2026

help-circle






  • I have a git repo with all my docker files, config, notes, etc. I have a main overview file covering the overall system and then a directory for each machine. I edit things on my local machine, then scp and ssh to the various remotes. Once I’m happy with my changes, I commit and push to my Forgejo install on my NAS in case my main computer fails. Secrets, passwords, and keys are in my Vaultwarden.

    I don’t use AI for it, but a local model could probably give me the commands to do whatever I wanted based on the repo.






  • 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.







  • Hi! I’ve been seeing your questions here and I think some basic terminology and background will help you out.

    I’m going to try and avoid too much “whell acktully”, but there will probably be some.

    A kernel is the core of any operating system, it usually provides basic hardware support for programs to use, and in the case of Linux, hardware drivers, filesystems, low level networking protocols and other very close to the hardware support.

    But a kernel can’t really do anything by itself, so we run programs on top of it. Some of these are also very low level and most people don’t deal with them or know they are there, while others are things like web browsers, video games, and whatever else you directly use every day.

    For Linux, there are often multiple programs that provide the same or similar functionality, with different features and tradeoffs, at all levels of the system. With Windows or Mac, there is often only one version of the low level programs that they provide and you never know is there.

    Because of all the options, different groups have put together different sets of these programs together, along with configuration files, and installer programs. These are called distros, short for distributions. Different distros make different choices for at least as many reasons as there are distros. Also in Linux, a program plus whatever files it needs are often called packages.

    Since even a small distro may contain thousands of packages, management of them is very important. Most distros have a package manager program to help deal with that and the package manager is how you will install most packages, though as always there are other options. A package manager is similar in some way to an app store from Mac or windows, only not shitty.

    Some distros make a lot of package choices for you, others make you make basically every choice. Most are somewhere in between. So-called beginner distros are usually ones that have made all the choices for you, and aimed those choices at being easy to use for people that have only experienced Windows or Mac.

    A desktop environment is an integrated graphical interface that has a bunch of programs that all work together and have a similar look and feel. You may also hear about a window manager, which is like a very minimal desktop environment that doesn’t come with a lot of features by itself.

    Different distros provide different desktop environments by default, or maybe none at all! Some make it very easy to switch from one to another, but some don’t.

    Most DEs try to look like either Windows or Mac in order to feel friendlier to new users. Window managers generally don’t, as they are assumed to by used by people with a lot of experience who want something very specific and will take the time to make it happen.

    Some common DEs and what they sorta look like are:

    • Gnome - Looks a lot like Mac, not particularly customizable, good keyboard only support
    • KDE - Looks a lot like windows by default, but quite customizable.
    • Cinnamon - Also looks like Windows, but forked off of an old version on Gnome a long time ago
    • LXDE - Also looks like windows by default, often used on very low end hardware
    • Cosmic - Looks like Mac but very customizable

    And here are some common distros and their default DEs

    • Fedora - KDE
    • Mint - Cinnamon
    • Debian - Offers a choice, but defaults to Gnome
    • Ubuntu - A custom version of Gnome, but also comes in a KDE and LXDE version
    • PopOS - Cosmic

    I hope this helps!