Sure, the docs are pretty minimal though: https://wiki.servarr.com/prowlarr/settings (just click on Proxy)

Basically you can configure a proxy (from your VPN provider for example) for each indexer (or font add a tag to apply it to all of them), and queries to indexers will run through there. This avoids Sonarr making calls to TVDB or whatever through the VPN and getting blocked.

Trash guides say you shouldn’t run the *arr’s through a VPN because you’re likely to get blocked by metadata servers. I only run my download client through the VPN + also use gluetun’s HTTP proxy for Prowlarr’s indexers

LFS?

Use gluetun, look up how to configure for your provider. Run a 2nd container for your torrent client, using network_mode: “service:gluetun” to run all your traffic though the vpn. Note that if you’re forwarding ports from your client to e.g. access the web UI, you’ll need to forward them from the gluetun container instead.

You uh… you might have chosen the wrong field if you hate displacing labour

An the issue is only inside the network? I’d complain to IT about that, yeah. Maybe they are overriding the DNS record with their own DNS server or something.

Can you set your own DNS servers on your client devices? Does cloudflare or quad9 resolve it?

Do you have a static IP? If not, have you tried some kind of dynamic DNS like DuckDNS?

A tale as old as tech

This is true. However many big maintained public images are multi-arch so down for ARM, and the fact that Docker runs in a VM on Windows and OSX when you install it doesn’t matter to most people. On Linux indeed it reuses the host’s kernel (which is why containers can be a lot lighter than VMs)

It’s not NAS specific, it’s platform independent - that’s the whole point. You have an application you want to run, and you package it all up into a docker image which contains not only the application but it’s dependencies and their dependencies all the way down to the OS. That way you don’t need to worry about installing things (because the container already has the application installed), all you have to do is allocate some resources to the container and it’s guaranteed* to work

*nothing is ever as simple as it first appears

One area where this is really helpful is in horizontally scaling workloads like web servers. If you get a bunch more traffic, you just spin up a bunch more containers from your server image on whatever hardware you have laying around, and route some of the traffic to the new servers. All the servers are guaranteed to be the same so it doesn’t matter which one serves the request. This is the thing kubernetes is very good at.

Edit: see caveats below

Fair enough! Do you cover your costs for it? I see you’ve got live stats - what’s your monitoring stack?

This is just really cool, I’d love to build an actually useful service like this and have it at least pay for itself but so many things are so daunting! (Payments, SRE, having a nice front end, …)

Wow really nice project! Do you work on this full time?

What exactly is Hyprland? I looked at the site quick but I couldn’t quite figure it out from the description.

Disclaimer: I’ve only ever used Linux servers, not really as a desktop beyond vanilla Ubuntu

This is definitely a job for templating, seems you’ve got the right tool to me!

So far I just hand roll my docker-compose (at home, anyway). However, docker-compose does also support overrides via yaml merging, maybe that’s worth looking into?

My idea with that is to have a base compose that configures also my services and then to have a few override yamls with environment specific stuff (like prod, local, …)

This is similar to Kustomize from kubernetes land which I’ve worked with in the past

Yep, k8s is for people who need regular capacity scaling and high availability. Self hosting images is a static website, perfect for an S3 bucket or similar

Funny, but feels unfair to mastodon (as someone who doesn’t use mastodon), they are definitely not trying to destroy the world and could use donations too!