frigate: Should not we store the database file in `/data` by default?

  1. /data is unique per add-on, which persists for as long as the add-on is installed
  2. Uninstalling the add-on would cause the database file to get deleted, which I think makes sense
  3. I suppose several people maps their /media/frigate folder to an external (potentially an much slower HDD) device. It isn’t smart to store the database in the HDD in this case.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

I think this change is probably a good idea. It just needs to be done very carefully.

Now… should it be done as part of the Frigate process, or should we do as a s6 oneshot/init service?

Feel free to work on it but just FYI I don’t believe it will be included in 0.12. We are looking to eventually break different processes into their own S6 processes along with the potential idea for zeromq so I think it would make sense as an S6 service init

But I’m all in for breaking changes as Frigate is still in 0.x. This is in accordance with SemVer, which expects breaking changes to occur in the development phase.

That’s fair, but as someone who works to support users in the issues it is not that simple and being in 0.x doesn’t change the time it takes to help users solve the breaking changes. Also, we’re trying to move away from breaking changes as it just makes things more difficult for everyone involved.