First, thank you for making this. Seems very useful… That being said I’m having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.

services:
  mixarr:
      container_name: mixarr
      image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0
      ports:
        - 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container
        - 3443:443
      volumes:
        - ~/mixarr-data:/data
      environment:
        - SESSION_SECRET=$(openssl rand -hex 32)
        - FRONTEND_URL=https://my-domain:3443/
        - BASE_URL=http://my-domain:3010/
      restart: unless-stopped

Edit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don’t need it built in.

That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.

Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.

You either don’t watch Gamers Nexus reviews or you watch them and genuinely don’t understand enough to know how in-depth his tests go.

LTT is garbage “entertainment” though. I’ll agree with that.

You can pretty easily point Lidarr to an alternate cache server. Either use the docker images they provide (link below) or of you already have Lidarr with plugins setup, you can do it that way (also explained in the link below)

https://github.com/blampe/hearring-aid?tab=readme-ov-file#-docker-images

Oh, the way it’s worded I thought you were calling it a neat filter that already existed.

I agree though. Would be a great filter.

I don’t see a filter for drive bays. I’m on mobile so maybe that’s why?