I run Adguard Home containers (the primary auto-syncs to the secondary) and use redirect filters to assign hostnames to each of my containers. I have a “services” folder of bookmarks for each container host so I don’t have to remember each service’s port number. I use KeePassXC to track all my passwords and certificates so authentication is a breeze (someday I’ll get around to setting up an SSO solution). I also keep a .txt file with my basic network info that doesn’t always translate well to dns hostname redirects in adguard. I occassionally remember to update my hosts listed in the file. My individual config files aren’t backed up beyond my automated container backups, but so far none of my services have been that complicated I couldn’t just rebuild from scratch.

It’s not perfect, but combined with my automated backups I have barely enough to rebuild if/when my hardware fails.

As far as I could tell: yes, and yes.

I wonder if this post has anything to do with the unmanic API outage earlier today, lol. I was pulling my hair out trying to figure out what I’d done wrong until I finally convinced myself there must be a cloud-side outage impacting the plugin browser. By the time I figured it out they came back online and the plugins were browsable again, but I lost hours over this stupid problem.

Today’s outage perfectly illustrated why we choose to self-host in the first place. I too would love to see a completely self-contained foss solution for this service. Some clever shell scripting is probably all you really need to perform automated ffmpeg calls, but individually containerized services are clearly what we all prefer. I do wish I had more time to code…