recyclarr VS gluetun

Recyclarr (GitHub) to automatically update custom formats per the TRaSH Guides. This took some tweaking to get just right, because it also changed my quality definitions, which I didn't want (YTS releases are fine for most of my users, lol).

(Sidenote - this is so I can utilise Recyclarr to sync profiles and formats from Trash guides - https://github.com/recyclarr/recyclarr)

There's also Recyclarr to automatically sync from the trash guides

[https://github.com/recyclarr/recyclarr.

It's also quite automateable: https://github.com/recyclarr/recyclarr

Capable of using TRaSH-Guides profiles for quality definitions and release profiles, similar to Recyclarr. If the TRaSH-Guides profile is updated, Buildarr will sync those updates to your instances.

I follow the TRaSH Guide, for the most part. I have custom formats set up using Notifiarr, and at this point, either using Notifiarr or Recyclarr custom formats is a necessity for any user. If you don't, your searches with Sonarr and Radarr are going to be all over the place.

I use https://github.com/recyclarr/recyclarr/pkgs/container/recyclarr which loads https://trash-guides.info/.

On point 3, I use Recyclarr to keep my release profiles synced up to Trash's current recommendations.

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki