• 1 Post
  • 213 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle

  • Add renovate bot (self-hosted or not) or a similar not to your nixos repository to automatically update your lock file. Enable automatic system rebuilds (not live, nixos-rebuild boot…) to keep in sync with the repo.

    Include multiple nixos systems in one repo, then reuse configuration or even make them reference each other (if you want that)

    Find an issue to report upstream (or even add a pull request)

    Fully automate your reinstall using disko and nixos-anywhere (don’t forget luks)

    Be happy (optional)

    Go over everything you’ve written in your repo so far, realise it’s formatted wrong and spend 2 hours fixing it until it no longer works

    Build a derivation for something that doesn’t exist (also add a pull request if applicable and you’ve got time to maintain it)

    Add a little nixpkgs-unstable, as a treat (use overlays)

    Backups

    Build a server so convoluted, kubernetes is easier to manage (I am here)















  • for a homelab I don’t think it’s feasible to fully review the source code of everything you install

    Here’s what you can actually do:

    • Consider if you actually need the application and stop applications you don’t use
    • Don’t allow public access unless it is necessary, consider VPN/reverse proxies with client authentication (if supported)
    • isolate applications that don’t need to talk to each other
      • see also rootless podman, firewalls, virtual machines, etc
      • don’t forget network access, if everything runs on 127.0.0.1 and every service shares it then they can all talk to each other! (See also network namespaces or VMs)
    • Don’t reuse passwords
    • keep software up to date
    • actually evaluate the quality of the project if it needs access to sensitive information
      • see open issues, closed issues that stand out
      • check for audits or at least a history of good effort™

    Sure you wont always catch ai slop this way but you don’t need to read a line of code to at least be reasonably sure your arr stack won’t get to the family photos.