jet's interesting finds

91 readers

1 users here now

my journal

founded 2 years ago

MODERATORS

jet@hackertalks.com

totallynotjet@lemm.ee

jetlag@dubvee.org

Nixarr - Media Server Nixos Module (nixarr.com)

submitted 6 days ago by jet@hackertalks.com to c/interesting@hackertalks.com

3 comments fedilink hide all child comments

This is a fun way to kill a few days learning nixos and setting up a home media stack.

I have done a tremendous amount of bikeshedding playing with this project. great fun

Finally justifying my home network over-building - all I had to do was try to move around 100gib objects constantly!

this module wraps a VPN namespace around (Seerr, Prowlarr, Sonarr/Radarr, (torrent/nzb), jellyfin), it's pretty declarative, there are some things that still manually need to be setup by hand (not the fault of nixos).

For extra complexity - My nixos is a thin os backed by NFS over 10g fibre, on a isolated vlan that can only egress the network to known wireguard ports.

I spent so much time trying to optimize bandwidth I ran out of things to download!

top 3 comments

sorted by: hot top controversial new old

[–] Scipitie@lemmy.dbzer0.com 1 points 6 days ago (1 children)

This looks fun! I have a similar setup but I've two VPN layers: qbittorrent and slskd behind a commercial VPN (with port forwarding, because a pirate be illegal in these waters). and then a VPN layer to access jellyfin and jellyseer remotely from trusted devices.

Just as inspiration for others who want to dive even deeper!

Although I've cheated a bit, the home layer is nixos native pretty much but qbittorrent runs as docker network layer because I really didn't want to fuck that part up :D

Thanks for sharing!

[–] jet@hackertalks.com 2 points 6 days ago* (last edited 6 days ago) (1 children)

Although I’ve cheated a bit, the home layer is nixos native pretty much but qbittorrent runs as docker network layer because I really didn’t want to fuck that part up :D

That is the beauty of nixarr, they already prefucked it, so it's done out of fucks!

I've aggressively been monitoring the nixos vm, and nothing is leaking at all. Qubes would be a fun way to do it too, but ain't nobody got time for that.

so you nest the VPNs A(B()) or you run them in parallel A()+B()? I suppose parallel. I had but this on my test network so it was A(B()) for awhile (test network is forced over a vpn), but now I'm pretty happy with vlan firewall +A()+B() based on namespaces and packet tagging in the kernel.

[–] Scipitie@lemmy.dbzer0.com 1 points 6 days ago

It's parallel, yeah - the anti government von is only for the download clients, my access from everywhere VPN is for, will, the machine itself - with the docker bridge having two interfaces.

In effect it's a gluetun docker network and Zerotier for the rest.