I recently replaced an ancient laptop with a slightly less ancient one.

  • host for backups for three other machines
  • serve files I don’t necessarily need on the new machine
  • relatively lightweight - “server” is ~15 years old
  • relatively simple - I’d rather not manage a dozen docker containers.
  • internal-facing
  • does NOT need to handle Android and friends. I can use sync-thing for that if I need to.

Left to my own devices I’d probably rsync for 90% of that, but I’d like to try something a little more pointy-clicky or at least transparent in my dotage.

Edit: Not SAMBA (I freaking hate trying to make that work)

Edit2: for the young’uns: NFS (linux “network filesystem”)

Edit 3: LAN only. I may set up a VPN connection one day but it’s not currently a priority. (edited post to reflect questions)

Last Edit: thanks, friends, for this discussion! I think based on this I’ll at least start with NFS + my existing backups system (Mint’s thing, which is I think just a gui in front of rcync). May play w/ modern SAMBA if I have extra time.

Ill continue to read the replies though - some interesting ideas.

    • Hawke@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      17 days ago

      Isn’t nfs pretty much completely insecure unless you turn on nfs4 with Kerberos? The fact that that is such a pain in the ass is what keeps me from it. It is fine for read-only though.

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        17 days ago

        Would be fine for designated storage networks that use IP whitelists.
        Other than that, you kind of need user specific encryption/segregation (which I beliege Kerberos does?)

      • nesc@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        17 days ago

        It is, but nfsv3 is extremely easy to configure. You need to edit 1 line in 1 file and it’s ready to go.