• 0 Posts
  • 51 Comments
Joined 9 months ago
cake
Cake day: August 14th, 2025

help-circle
  • Make it maintainable.

    Documentation. Or implicit documentation with ansible or the like (opentofu).

    Separate things with LXCs or VMs or OSI containers. Maybe firewalls (ufw) and VLANs to separate them. Incus is nice. As someone already said: Leave the host system mostly vanilla. Services go in the virtual boxes and containers.

    Btw: Nix looks promising, too. But I have not opened that can of worms, yet.

    Backups…

    Automation. unattended-upgrades, watchtower(unmaintained) or the like. So you don’t have to do it yourself and then forget about it. Claude is looming on the horizon. It will bring many bugs to light and code the exploit for it in no time if someone asks for it nicely.



  • You are right. Backup and storage of scans should be not a big deal.

    But the paper documents:

    Some things like birth and education certificates need to be kept indefinitely. Some documents like receipts need to be kept for a while. Some documents can be discarded after scan and some are PDFs entirely.

    I. E. How can I tell from the scan if there is a paper document and where is it stored?

    Or How do I age out paper which is not needed any more?


  • The decision is yours to make. You didn’t say if power consumption is important - if you keep the server on 24/7 it could be relevant. It’s hard to say if you can modify the server, to make it quieter. Or if you can salvage parts. Or if you need all the CPU performance of a server CPU.

    If you want to keep it or salvage parts: In my experience the fans are the noisy part of a server. I don’t know the form factor of the main board or the case. I really can’t say which parts you can keep and which need replacing.

    120mm fans with pwm are better than 40mm fans at full speed. Bigger heat sinks, too.

    If not: You can always try to sell the server and get a low power single board computer with enough (32GB+) RAM instead (hardkernel h4 or a cheap chinese alternative). IMO a celeron N is fast enough to run multiple VMs (or better: containers). The limiting parts are RAM and storage. Things like transcoding videos will take more time than on a server CPU… But immich and an *arr stack will work flawlessly for a one or two user instance.




  • I like the app. Thanks for sharing.

    trying to reduce the explicit drinking water target based on what you ate

    I think this is/ was my plan, yes.

    This is not a feature request. I was just wondering where the water intake is tracked. As part of a recipe or food would’ve felt natural to me. Hence the question. I missed the water sub tab in the diary tab’s top right corner.

    My feedback:
    Cooked noodles, soft drinks, a cup of coffee with sugar, a glass of water with lemon juice, protein shakes would be examples for “watery” food.

    Right now one can keep track of the nutrients + fibre + x in food in one calculation. And then there is a second tracking just for water.

    Two lists feel more complicated than one list. To add a cup of coffee I need to add the nutrients part (sugar, coffein, fat) as a food entry in the diary tab + a cup of water in the water sub tab.

    Currently no, there’s no per-food water field in NutriTrace, and food water doesn’t count toward your daily water goal.

    Thanks. Fine by me. :)
    I could add a custom nutrient “water” to my foods and recipes to achieve what I planned. Or I just ignore water intake tracking.














  • Netplan config? Sure:

    network:
      ethernets:
        enp35s0:
          dhcp4: false
        enp36s0:
          dhcp4: false
      vlans:
        enp35s0.100:
          id: 100
          link: enp35s0
          dhcp4: false
        enp35s0.101:
          id: 101
          link: enp35s0
          dhcp4: false
      bridges:
         br0:
    	   # untagged
           interfaces: [enp35s0]
           dhcp4: false
         br0.100:
    	   # vlan 100
           interfaces: [enp35s0.100]
           dhcp4: false
         br0.101:
    	   #vlan 101
           interfaces: [enp35s0.101]
           dhcp4: true
      version: 2
    

    I’m not sure if the version-property is still required. The only interface with an IP is br0.101. Opnsense provides DHCP (v4).

    You can attach multiple ethernet-devices to a bridge (which I did not):

          br0.100:
            interfaces:
              - enp35s0.100
              - two
    	        - three
    

    I’m not sure if you can attach the docker bridge via netplan - it has to exist at boot time, I think. My docker containers run inside a VM (kvm) with one interface, which sits in one of the VLANs. The VM’s interface is a bridge device (br0.100). The VM ethernet device is attached to the bridge, it receives its IP from the router and behaves like a real server.