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?

  • tofuOPEnglish
    2·
    2 months ago

    Maybe you could just spin down/turn off the disks? That will reduce power consumption a lot and they’ll get up once requested.

        • AtariDump@lemmy.worldEnglish
          1·
          1 month ago

          Power consumption.

          Plus, I don’t think an enterprise grade server is designed to spin down the disks when they’re not in use.

          • tofuOPEnglish
            1·
            1 month ago

            You can just do that yourself regardless of what the server was intended to do, with a cronjob for example. You can also set an idle time after which it spins down with hdparm but that doesn’t always work for different reasons.