• 2 posts
  • 10 comments
Joined 1 year ago
Cake day: June 9th, 2025
  • I am taking precautions to have my setup easily deployable no matter the hardware. The only real documentation becomes mountpoints and such for external storage.

    For DNS and Reverse Proxy entries, I have those automated. Any time I spin up a new docker container, that information is deployed with labels. Also entries into my homepage.

    The .env files contain any variable I would want to store to make my setup portable, shareable and not have to worry about leaking any of my information. Not that it would be end of the world considering nothing really leaves my network unless it is through my VPN.

Greetings Lemmings,

I realize that self-hosting for many is just a hobby. Something they do for fun. And the topic of today is usually a “not-so-fun” part of the IT industry.

Jump Scare Warning

Documentation

I have for so long just let my lab grow organically. And months down the road an issue pops up with a service, and I have no idea how I set something up, and may not have documented it. Whether that be comments inside of configuration files, or via other means.

I have gotten marginally better at documenting within the config files or code that I am writing. However, I don’t want just that as an option. So I spun myself up a Bookstack container.

I am slowly going through and creating what would amount to a full blown wiki for my setup. Doubly I can use this as part of my resume.

So I ask of you; what ways do you prefer to document? How do you keep yourself honest, and actually stick to it.

  • I like having as many apps accessible via the browser as possible. Makes it portable for me.

    No matter how many machines, experience is the same. With these apps, I can allow other users access.

    Its accessible through my phone as well that way.

    And if I ever have to reinstall my OS its quicker because of less that I need to install. And on top of that I only update that one container vs updating every machine I have a program installed to.

  • I did putz around with Picard way back but didnt stick with it because of its UI. Though I may set up a docker container just to have the option to use it…

    Navidrome + Feishin for desktop + Symfonium for Android is the route I went too.

    Though I am playing with Tempus as well for Android too. Its a nice Open Source option.

    Degoogling my life was a motivator to self host.

Greetings Lemmings!

I am not new to self hosting; been at it for a few years. And I have neglected a very important part of my home lab; MUSIC!

So I stream music from Navidrome to all of my devices.

My music library has grown organically over the years, for probably the past 17 years. And a few times I had manually organized and fixed up some of the tags. But ultimately I ended up with a mess of a library.

I am working on cleaning that up. Though I absolutely should have cleaned it up before I created 2 backup scripts.

In short, I have a script that is called from a systemd service on a timer that runs my backup script that essentially more or less uses rsync to mirror the files in LiveMusicDir to MusicArchive1. This happens on my docker host where my Navidrome lives. The Music is on an NFS share hosted outside of the docker host.

The next step I run another similar setup on my desktop; systemd service running a script on a timer that uses rsync and other dependencies to track changes.

What I plan to do is organize the source. I am using beets, and learning as I go.

What methods do you use for managing a large music library?