Bitwarden/vaultwarden is a popular option for selfhosters.
- 0 Posts
- 5 Comments
Ebby@lemmy.ssba.comto Selfhosted@lemmy.world•Realities of hosting a tor relay node at homeEnglish0·18 days agoI ran a relay too way, way back in the day and I remember almost a third of the sites I used blacklisted my IP address within days. It wasn’t cool.
I ended up shutting it down, resetting my cable modem, and spoofing a new MAC address on my router to get a new IP address to get everything working again.
Using a VPN is smarter. I wouldn’t run that on IPv6 whatsoever.
I just did something sort of like what you are doing and after a few hiccups, it’s working great. My Synology just couldn’t handle transcoding with docker containers running in the background.
Couple differences from your plan: I chose a N100 over the N150 because it used less power and I wasn’t loading up CPU dependent tasks on the thing. The N150 is about 30% faster if memory serves, but draws more power. Second, do you really need a second m.2 SSD BTRFS volume? Your Synology is perfectly capable of being the file storage. I’d personally spend the money you’d save buying a smaller N150 device on a tasty drive to expand the existing capacity then start a second pool from scratch.
Finally, I wouldn’t worry about converting media unless you are seriously pinched for space. Every time you do, you lose quality.
Ditto to your comment except power usage. I moved my Plex/Jellyfin (and hopefully Immich soon) docker containers to an N100 for the hardware acceleration. TDP is 6 watts on some of these devices and CPU use sits around 2% unless Plex is doing DB optimizations (about 60% for a bit). I haven’t measured consumption or my older server, but I feel moving some CPU intensive services to hardware GPU is saving a few watts.
That’s the route I took too. NAS for storage and simple docker containers, Minipc for compute/GPU.