I am not responsible for any malicious or illegal use of this configuration, use it at your own risk.

This docker-compose can be used to spin up :

• A VPN (using gluetun)
• Jackett for torrent indexing
• Sonarr and Radarr for automatic management and download
• Jellyfin to manage the media library
• qBittorrent for torrent downloading
• Jellyseer for easier usage

1. Run make .env to create the environment files.
2. If you want to use a VPN, you need to set some variables in vpn.env, you can see gluetun's wiki for reference. For ProtonVPN, for instance :

VPN_SERVICE_PROVIDER=protonvpn
OPENVPN_USER=<user> # from https://account.proton.me/u/0/vpn/OpenVpnIKEv2>
OPENVPN_PASSWORD=<password>
SERVER_COUNTRIES=Netherland

3. Run make up (or docker-compose up) to spin up the services.
4. The services can then be managed using docker-compose normally.

The services configuration will change depending on whether or not he VPN is used :

• With the VPN, all services are internally available through localhost
• Without the VPN, you need to set them up using the name of the services as host

You can run make <service>.api-key to retrieve api keys for *rr services and Jackett. For instance, the Radarr API Key is obtainable through make radarr.api-key.

I would recommend using a VPN to avoid issues, such as with your ISP. However, it is possible to use this without a VPN.

To disable it, simply run make vpn.disable then make up to start the services again (they will be automatically stopped beforehand). You can then enable it again using make vpn.enable.

Adding a service requires a few modifications :

• Adding the service itself in the docker-compose file
• Adding the port to the VPN service
• Adding the service name to the list of services in the Makefile
• Creating the corresponding service.env file (this is done automatically by make .env but if the .env file already exists this won't work)

Configuration is then intended through env files, specifically <service>.env