Improvement to the sync_recordings option? #21310
Description
Sorry for the new issue but had an idea :), what about adding an additional option like "sync_recordings: full_reset" which would clear the db and clear off recordings as-well, while still preserving the user sections in the db, this way manually deleting the db or files wouldn't even be needed, and a clean soft-reset can all be done from the frigate ui.
The only reason I need this is that one of my dumb cameras starts recording fast for some odd reason, like the 10 second clip plays 60 seconds like in fast-forward, then starts to screw up the bandwidth reporting stats and even the timeline gets messed up, so far haven't found a fix for it yet. I can manually search out the bad clips but more often it's quicker just to clear everything and start fresh
Storing users and passwords in a database is standard practice for most apps, and Frigate is no different. Splitting credentials into a separate store adds complexity and its own failure modes without much practical benefit.
In theory, you could preserve users/passwords by exporting/importing the user table, for example.
If you want to avoid reconfiguring users when resetting the database, using a reverse proxy with header-based authentication is the recommended approach. That allows authentication to live outside Frigate entirely while keeping the core database disposable.
Originally posted by @hawkeye217 in #21307