stuner

@stuner@lemmy.world

• ⁨Comment⁩ on ⁨Looking for recommendations for a multi home NAS solution⁩ ⁨⁨17⁩ ⁨hours⁩ ago⁩:

  Read (only) access should be fine. What makes it complicated is if there can be writes from multiple locations. Basically, the simple version would be to just periodically copy the data from the primary to all secondary locations.

• ⁨Comment⁩ on ⁨Looking for recommendations for a multi home NAS solution⁩ ⁨⁨18⁩ ⁨hours⁩ ago⁩:

  I can see why you’d want to go with an off-the-shelf NAS. But, I would carefully check if it supports your use case, as it’s quite advanced.

• ⁨Comment⁩ on ⁨Looking for recommendations for a multi home NAS solution⁩ ⁨⁨20⁩ ⁨hours⁩ ago⁩:

  If the data only needs to be read & written from a single server (and the others are just backups), you can also use simpler replication instead of synchthing. E.g. syncoid or TrueNAS replication. It sounds like you should be able to do that with separate datasets per household in your usecase.

• ⁨Comment⁩ on ⁨Looking for recommendations for a multi home NAS solution⁩ ⁨⁨21⁩ ⁨hours⁩ ago⁩:

  I would probably go with a simple approach like this:

  • ZFS: Each house gets a “NAS” that provides a ZFS filesystem to store the data. This gives you the ability to share the drives across your use cases (you, rest of the family), snapshots, RAIDZ support, and usage quotas. For the OS, you could use what you prefer (TrueNAS, Debian, Ubuntu, …).
  • Syncthing to synchronize the files across the servers/houses. This allows you to read and write data from anywhere and syncthing will mirror the writes to the other places. I use it to synchronize data across 5 devices and it works quite well.

  There are probably more advanced (enterprise?) ways to handle the file synchronization. But, I think this hould be good enough for normal, personal use. The main disadvantage is that you’re only synchronizing the current data (excluding the ZFS snapshots). On the other hand, this also allows you to mix file systems if necessary.

• ⁨Comment⁩ on ⁨How to move OwnCloud data?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  I’m not quite sure what you’re trying to do here. Are you

  1. Trying to create a new owncloud instance and put your data somewhere other than in /var, or
  2. Try to move the data location of an existing owncloud instance?

  If you’re trying to do the second one, there’s a useful guide on it here: omiid.me/…/move-docker-volume-to-bind-mount. The first one should be even simpler, you can just replace the volumes in the compose file by bind mounts (basically, just this step of the tutorial: omiid.me/…/move-docker-volume-to-bind-mount#modif…).

• ⁨Comment⁩ on ⁨Multilingual people all must have experienced YouTube's f**kery with auto translation. Still no workaround?⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  Yeah, I also find it very annoying. I guess Youtube just can’t imagine that people exist who speak more than one language…

  Having the option of automatic translations is fine but at least let me disable it!

  I think, currently, creators can disable it, so you can ask them to do that.

• ⁨Comment⁩ on ⁨Prioritizing de-clouding efforts⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  Forgejo becase a hard fork about a year ago: forgejo.org/2024-02-forking-forward/ And it seems that migration from Gitea is only possible up to Gitea version 1.22: forgejo.org/2024-12-gitea-compatibility/

• ⁨Comment⁩ on ⁨good replacement options power efficiency and affordable "large" storage⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  That system also sounds a lot more capable than mine. How did you end up with 25 VMs?

• ⁨Comment⁩ on ⁨good replacement options power efficiency and affordable "large" storage⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  I’m running it in a regular mATX case (Node 804) but I think you can also get AM5 motherboards in rack-mount cases.

• ⁨Comment⁩ on ⁨good replacement options power efficiency and affordable "large" storage⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  Perhaps my recent NAS/home server build can serve as a bit of an inspiration for you:

  • AMD Ryzen 8500G (8 cores, much more powerful than your two CPUs, with iGPU)
  • Standard B650 mainboard, 32 GB RAM
  • 2 x used 10 TB HDDs in a ZFS pool (mainboard has 4x SATA ports)
  • Debian Bookworm with Docker containers for applications (containers should be more efficient than VMs).
  • Average power consumption of 19W. Usually cooled passively.

  I don’t think it’s more efficient to separate processing and storage so I’d only go for that if you want to play around with a cluster. I would also avoid SD cards as a root FS, as they tend to die early and catastrophically.