frigate: enables nginx.recommendedProxySettings by default

[nagisa]

Describe the bug

When I enabled frigate in my system that otherwise also uses nginx, I was surprised to find that some of the nginx servers I had suddenly were broken (and returning 400s.) Namely headscale.

I had to go to those specific nginx servers and set services.nginx.virtualHosts.headscale.locations."/".recommendedProxySettings = false; in order to keep things working.

I think frigate should not be enabling this option globally and instead set it for each individual location it specifies in order to not interfere with other virtualHosts.

Steps To Reproduce

Steps to reproduce the behavior:

1. Specify a virtualHost manually, build config, check generated nginx conf to see absence of recommendedProxySettings include;
2. Enable frigate, rebuild;
3. nginx config now contains recommended proxy settings includes for all server blocks/locations.

Expected behavior

Enabling frigate does not affect other nginx servers in any way.

Screenshots

N/A

Additional context

N/A

Notify maintainers

no meta key in the frigate module.

Metadata

• system: "x86_64-linux"
• host os: Linux 6.8.6-zen1, NixOS, 24.05 (Uakari), 24.05.20240519.6c0b7a9
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.18.2
• nixpkgs: /run/current-system/nixpkgs

---

Add a 👍 reaction to issues you find important.

[nagisa]

My jellyfin setup also appears to be affected by this.