Last working config #8891
Replies: 2 comments 6 replies
-
This will only work if you edit your config in the frigate editor. I do not use the internal editor. |
Beta Was this translation helpful? Give feedback.
-
The built-in config editor has config validation before it allows saving. If you're not using it then the burden is on you to not mess your config up, I don't see a reason for frigate to do this when it already has a config editor that will make sure you can't save a broken config. |
Beta Was this translation helpful? Give feedback.
-
We've been all there... make a change or two to your config, restart Frigate and IT BOMBS, somebody is unhappy!
"What did I change and need to revert or back out??"
I recently made a change to my object list ("This is "safe" change, no need to copy my current config..."), saved with no yml editor grip messages and then my Frigate container would not start, caught in a docker restart loop.
Wasn't my first rodeo so I've learned to copy the current config.yml to last_know_working_config.yml before restarting, AND keep my config directory outside of the container/image, so I could quickly fix/revert the bad config outside of Frigate, and get back up and running.
What would be a great new feature would be for the Frigate to do a lot of that automatically. Save the current config to before any edit saves. Then there would always be a history of changes and you could pick a prior and get back up and running. And once Frigate gets to a fully up and running state, it copies the current config to "last_working_config.yml".
Best and most elegant would be if a git repository was detected in the config folder, a git commit (git part of the Frigate image) was performed on each config edit save.
Beta Was this translation helpful? Give feedback.
All reactions