With the recent discussions around replacing Spotify with selfhosted services and the possibilities to obtain the music itself, I’ve been finally setting up Navidrome. I had to do quite a bit of reorganization to do with my existing collection (beets helping a ton) but now it’s in a neatly organized structure and I’m enjoying it everywhere. I get most of my stuff from Bandcamp but I have a big catalog from when I’ve still had a large physical collection.

I’m also still working on my docker quasi gitops stack. I’ve cleaned up my compose files and put the secrets in env files where I hadn’t already, checked them into my new forgejo instance and (mostly) configured renovate. Komodo is about to get productive but I couldn’t find the time yet. Also I need to figure out how to check in secrets in a secure way. I know some but I haven’t tried those with Komodo yet. This close of my fully automated update-on-merge compose stacks!

I’ve also been doing these for quite a while and decided to sometimes post them in !selfhosting@slrpnk.net to possibly help moving a bit from the biggest Lemmy instance, even though this community as it is is perfectly fine as well as it seems.

What’s going on on your servers? Anything you are trying to pursue at the moment?

  • AtariDump@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    Trying to figure out how to drop my energy requirements and still keep ~100TB running.

    Right now it’s 12x 10TB drives in a RAID 6 with ~8TB still available; it might be time to bite the bullet and upgrade to 20TB drives. Problem is, if my calculations are correct, I’d still need 7 drives - 5 X 20TB=100TB and then two more drives for “parity”.

    The server I have lined up already has a PERC in it.

    • Jason2357@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 days ago

      Do you actually need 100TB instantly available? Could a portion of that be cold storage that can be booted quickly from a WOL packet from the always-on machine when needed? With some tweaking, you could probably set up an alpine-based NAS to boot in <10 seconds, especially if you picked something that supported coreboot and could avoid that long bios post time.

      • AtariDump@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Don’t need the 100TB instantly. Most of the Linux ISOs are more for archival reasons.

        Talk to me more about this NAS with WOL. :-)

        • Jason2357@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 hours ago

          Most motherboards support wake packets sent over Ethernet. They only work on your lan, but they will start a machine or wake it from sleep. Sending a packet from another machine is fairly simple, it’s old tech. I’ve seen simple web servers that have a “send wake” button, but you could probably trigger it from a variety of things

          • AtariDump@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            6 hours ago

            The WoL part I’ve got.

            It’s the NAS with ~10 second boot time that can house enough drives for 80TB of data which would be triggered and accessible to a plex server when needed that I’m more interested in.