Exactly. I have my firewall set up to block everything I don’t explicitly allow through. That way if I’m a little loose with running things on ports, it at least won’t leak ports past the firewall.

It’s fine, it just grabs the network settings from the gluetun service.

Btw, your post is hard to read due to formatting. Surround the code block with triple backticks at the top and bottom like this:

```
code goes here
```

Example:

services:
  gluetun: # This config is for wireguard only tested with AirVPN
    image: qmcgaw/gluetun
    container_name: gluetun
    ...
    ports:
      - 8888:8112 # deluge web interface
      - 58846:58846 # deluge RPC
  deluge:
    image: linuxserver/deluge:latest
    container_name: deluge
    ...
    network_mode: service:gluetun

They’re also slightly cheaper since they don’t take any profit from their registrar side, hoping to make it back with other services.

I was with Namecheap for years, and they’re totally fine. I am now with Cloudflare because they’re a bit cheaper and their API is well supported in various tools, and they also seem fine.

Yeah, nobody other than Brits use fortnightly anymore.

Reminds me of the suckless project, but for web stuff.

You don’t have to revert 8 services, you can stop/start them independently: docker compose stop <service name>.

This is actually how I update my services, I just stop the ones I want to update, pull, and restart them. I do them one or two at a time, mostly to mitigate issues. The same is true for pulling down new versions, my process is:

1. edit the docker-compose file to update the image version(s) (e.g. from 1.0 -> 1.1, or 1.1 -> 2.0); I check changelog/release notes to check for any manual upgrade notices
2. pull new images (doesn’t impact running services)
3. docker compose up -d brings up any stopped services using new image(s)
4. test
5. go back to 1 until all services are done

I do this whenever I remember, and it works pretty well.