Some fancy case options depending on your needs: Shop Inux3d
Added passive cooling for PI running HA and never encountered any issues.

I used VMs some time ago but never managed to look deeper into separation of bare metal vs VMs. Hence I can’t assess this reasonably.
Docker got me interested when it started and after discovering its networking capabilities I never looked back.
Basically I’m trying to minimize the possibility that by intercepting one dockerized service the attacker is able to start interacting with all devices. And I have lots of devices because of a fully automated house. ;) My paranoia will ensure the constant growth of privacy and security :)

Guessing it is more a habit from back in time when ssl certification wasn’t common. Panic of MITM attacks, friends sharing their trusted access to other friends, etc. all contributed to my actual status of paranoia.
Don’t make me reconsider my cybersec approach ;)

Rotating passwords only for web services. Vaultwarden does make it easy. Not all services allow 2FA.

I’m somewhat paranoid therefore running several isolated servers. And it’s still not bulletproof and will never be!

• only the isolated server, ie. no internet access, can fetch data from the other servers but not vice versa.
• SSH access key based only
• Firewall dropping all but non-standard ports on dedicated subnets
• Fail2ban drops after 2 attempts
• Password length min 24 characters, 2FA, password rotation every 6 months
• Guest network for friends, can’t access any internal subnet
• Reverse proxy (https;443 port only)
• Any service is accessed by a non-privileged user
• Isolated docker services/databases and dedicated docker networks
• every drive + system Luks-encrypted w/ passphrase only
• Dedicated server for home automation only
• Dedicated server for docker services and reverse proxy only
• Isolated data/backup server sharing data to a tv box and audio system without network access via nfs
• Offsite data/backup server via SSH tunnel hosted by a friend

Guessing, millions of people will feel obligated to share their ID. Not everyone can be saved

Original link:

https://technomagnus.vercel.app/posts/ultimate-privacy-list/

Check if Lidarr adds an artist* image in artist folder or add an integration for fetching images.

https://www.navidrome.org/docs/usage/artwork/#artists

https://www.navidrome.org/docs/usage/external-integrations/

Make sure the SQL server is not writing/blocking any files: docker-compose stop vaultwarden

Backup that specific folder to another destination and restart docker-compose up -d

I think you can’t track data corruption either because you will find out only when it occurred. Same is valid for SMART values as you correctly state. I believe it is a mix of using zfs, ECC and SMART monitoring.
https://phoenixnap.com/blog/data-corruption

Thanks for clarifying the intricacies connected to SMART monitoring.

SMART value monitoring helped me finding faulty drives, not only once. And drives are tested before adding to a production system.
Certainly system drives are separate from data drives. The latter can be perfectly monitored by SMART values.

If you want regular automatic hdd checks and don’t need a WebUI I recommend https://github.com/smartmontools

At last we keep it simple ;)

I set up custom bash scripts collecting information (df, docker json, smartCTL etc) Either parse existing json info or assemble json strings and push it to Homeassistant REST api (cron) In Homeassistant data is turned into sensors and displayed. HA sends messages of sensors fail.
Info served in HA:

• HDD/SSD (size, smartCTL errors, spin up/down, temperature etc)
• Availability/health of docker services
• CPU usage/RAM/temperature
• Network interface/throughput/speed/connections
• fail2ban jails

Trying to keep my servers as barebones as possible. Additional services/apps put strain on CPU/RAM etc. Found out most of data necessary for monitoring is either available (docker json, smartCTL json) or can be easily caught, e.g.

df -Pht ext4 | tail -n +2 | awk '{ print $1}

It was fun learning and defining what must be monitored or not, and building a custom interface in HA.

Your friends will comment on interface when you share music to them :)
Hardly using the UI myself ;)

Had for years airsonic, later airsonic advanced. The overhead is huge compared to Navidrome.
Had never an issue with Navidrome and it is much snappier. No even starting to talk about the modern interface compared to Airsonic.

You are right Beets doesn’t allow for custom id3v2 fields.
However it has quite a lot of fields ‘’’beet fields’’’
You can write them specifically using ‘’’-F’’’
(Beets doc)[https://beets.readthedocs.io/en/stable/reference/cli.html#fields]
I’m not aware of a publisher nor producer field though.

Lidarr can be used for tagging too and it does have a web interface.
Cleaning a messed up library with Beets is tough and depends on how the individual files are sorted. Start importing/organizing a small part or some albums to find out how it works. And a backup of data is always recommend!

I can recommend Navidrome. Organizing of library with Lidarr and (Beets)[https://beets.io]
I’m using Beets for tagging because of the Discogs plugin.
Lidarr for visual overview of the library.

Just put all commands into a bash file. Starting with ‘’docker tag’’ changing tag to something else in case I need to revert and than pull, compose up. All run by crontab weekly. In case something breaks the latest working container is still there.