Replies: 3 comments 3 replies
-
How does the sqlite database help? Currently my /config folder is mapped to one location with my config file and my /clips mapped somewhere else. I can easily use docker to map my /clips to a network share if I needed too. Wouldn't having your config in a sqlite format make it more complicated to update and maintain than plain text yml file? I could understand using sql if you wanted to do a mass camera update to enable or disable a feature but can't see much use from your suggested scenario. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/blakeblackshear/frigate/tree/release-0.8.0 Database If you are storing your clips on a network share (SMB, NFS, etc), you may get a database is locked error message on startup. You can customize the location of the database in the config if necessary. |
Beta Was this translation helpful? Give feedback.
-
IMHO regarding the docker deployment ... adding a bit more context to the database mapping would greatly help many since its mapped into /media in the provided examples.. By default you map external filesystem to hold clips, event, recordings etc as the container size is locked and any restarts would blow away these files if there was space. Changing the default example to map the to a local storage resource similar to the config.yml mapping and writeable would benefit everyone going forward and prevent the "database is locked" error... |
Beta Was this translation helpful? Give feedback.
-
Allow sqlite database configuration so there is an option to keep the database on local storage and store clips in different storage like network share. Or allow using existing database service like mySql?
Beta Was this translation helpful? Give feedback.
All reactions