skilltheamps

@skilltheamps@feddit.org

• ⁨Comment⁩ on ⁨Every single time I think of restructuring my homelab storage. What do you use for storage engines and how does it benefit you?⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  You need to ask yourself what properties you want in your storage, then you can judge which solution fits. For me it is:

  • effortless rollback (i.e. in case something with a db updates, does a db migration and fails)
  • effortless backups, that preserve database integrity without slow/cumbersome/downtime-inducing crutches like sql dump
  • a scheme that works the same way for every service I host, no tailored solutions for individual services/containers
  • low maintenance

  The amount of data I’m handling fits on larger harddrives (so I don’t need pools), but I don’t want to waste storage space. And my homeserver is not my learn and break stuff environment anymore, but rather just needs to work.

  I went with btrfs raid 1, every service is in its own subvolume. The containers are precisely referenced by their digest-hashes, which gets snapshotted together with all persistent data. So every snapshot holds exactly the amount of data that is required to do a seamless rollback. Snapper maintains a timeline of snapshots for every service. Updating is semi-automated where it does snapshot -> update digest hash from container tags -> pull new images -> restart service. Nightly offsite backups happen with btrbk, which mirrors snapshots in an incremental fashion on another offsite server with btrfs.

• ⁨Comment⁩ on ⁨Selfhosting Sunday! What's up?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Rootless podman cannot bind ports <1024, only root can by default (on pretty much any distro I guess). Have you done something like sysctl net.ipv4.ip_unprivileged_port_start=80 to allow non-root processes to bind to port numbers >=80?

• ⁨Comment⁩ on ⁨Immich 2.1 Released with Better Slideshow Shuffle, New Notifications⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  That’s what I thought, but last time I looked I only saw a “release” tag, no “v2” tag. Did I miss something?

• ⁨Comment⁩ on ⁨Immich 2.1 Released with Better Slideshow Shuffle, New Notifications⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  That server is also a homeserver I manage for family (in another city). The two homeservers then mutually back up each other.

• ⁨Comment⁩ on ⁨Immich 2.1 Released with Better Slideshow Shuffle, New Notifications⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  They show images from the same day in past years. So if your library has no images >= 1 year old I’m not sure if anything shows up.

• ⁨Comment⁩ on ⁨Immich 2.1 Released with Better Slideshow Shuffle, New Notifications⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  The same way as all other services: all relevant data (compose.yml and all volume mounts) are in a btrfs subvolume. Every night a snapshot gets made and mirrored to a remote server by btrbk.

• ⁨Comment⁩ on ⁨How do you keep up?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  This is not practical for a home setup. Not because it would be expensive for more hardware or whatever, but because as soon as you have multiple systems doing the same thing, their state diverges and for pretty much anything that is popular for selfhosting you cannot merge them again or mirgrate users between them without loosing anything. Distributed databases alone are a huge pita, and maintaining such redundant setups would be a million times more effort than just making sure that you can easily and quickly atomically roll back failed updates

• ⁨Comment⁩ on ⁨Engineer turns old 3D printer into a tattoo gun that you definitely shouldn't use at home⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  Yes, although I think auto “bed” leveling with a bltouch-style probe could work to compensate that