Files
frigate/frigate/util
Josh HawkinsandGitHub c88434dc29 Write migrated config atomically (#24926)
* write migrated config atomically

Config migration rewrote config.yml in place with open("w") after each step, so nginx's get_nginx_settings.py, which starts alongside frigate, could read an empty file, get None from yaml.load, and crash on config.get. Each step now writes to a temp file with the original mode and os.replace's it into place.

* keep config owner and handle file bind mounts in migration writes

os.replace failed with EBUSY when config.yml was a file bind mount, as in the documented --validate-config command, and the replaced file lost its original owner when Frigate ran as root. The write now copies in place on EBUSY and restores the original owner when permitted. Tests cover a failed dump leaving the original config and the bind-mount fallback.

* follow config symlinks in migration writes
2026-11-09 13:56:34 -07:00
..
2025-08-16 10:20:33 -05:00
2026-10-16 13:49:16 -06:00
2026-10-16 13:49:16 -06:00
2026-09-28 13:45:05 -06:00
2026-09-20 12:45:24 -06:00
2026-07-06 12:28:02 -05:00
2025-07-07 06:35:55 -06:00