frigate/.gitignore

.DS_Store
__pycache__
.mypy_cache
*.swp
debug
.vscode/*
!.vscode/launch.json
config/*
!config/*.example
models
*.mp4
*.db
*.csv
frigate/version.py
web/build
web/node_modules
web/coverage
core
!/web/**/*.ts
.idea/*
.ipynb_checkpoints
feat!: web user interface 2021-01-09 11:26:46 -06:00			`.DS_Store`
Removed usage of PyYAML for config parsing. (#13883) * Ignore entire __pycache__ folder instead of individual .pyc files Ignore .mypy_cache in git * Rework config YAML parsing to use only ruamel.yaml PyYAML silently overrides keys when encountering duplicates, but ruamel raises and exception by default. Since we're already using it elsewhere, dropping PyYAML is an easy choice to make. * Added EnvString in config to slim down runtime_config() * Added gitlens to devcontainer * Automatically call FrigateConfig.runtime_config() runtime_config needed to be called manually before. Now, it's been removed, but the same code is run by a pydantic validator. * Fix handling of missing -segment_time * Removed type annotation on FrigateConfig's parse I'd like to keep them, but then mypy complains about some fundamental errors with how the pydantic model is structured. I'd like to fix it, but I'd rather work towards moving some of this config to the database. 2024-09-22 10:56:57 -05:00			`__pycache__`
			`.mypy_cache`
Use dataclasses for config handling Use config data classes to eliminate some of the boilerplate associated with setting up the configuration. In particular, using dataclasses removes a lot of the boilerplate around assigning properties to the object and allows these to be easily immutable by freezing them. In the case of simple, non-nested dataclasses, this also provides more convenient `asdict` helpers. To set this up, where previously the objects would be parsed from the config via the `__init__` method, create a `build` classmethod that does this and calls the dataclass initializer. Some of the objects are mutated at runtime, in particular some of the zones are mutated to set the color (this might be able to be refactored out) and some of the camera functionality can be enabled/disabled. Some of the configs with `enabled` properties don't seem to have mqtt hooks to be able to toggle this, in particular, the clips, snapshots, and detect can be toggled but rtmp and record configs do not, but all of these configs are still not frozen in case there is some other functionality I am missing. There are a couple other minor fixes here, one that was introduced by me recently where `max_seconds` was not defined, the other to properly `get()` the message payload when handling publishing mqtt messages sent via websocket. 2021-05-22 17:28:15 -05:00			`*.swp`
initial refactoring 2019-02-25 20:27:02 -06:00			`debug`
Set User Agent for FFmpeg calls (#4555) * Set User Agent for FFmpeg calls * Allow to use shell-like string args * Add test for arg as string with space 2022-11-30 16:53:45 -06:00			`.vscode/*`
			`!.vscode/launch.json`
Migrate default database path from `/media/frigate` to `/config` (#5219) * Migrate db path to /config * Ensure oneshot runs * Put logic inside of Frigate's run * Use new db default path in code * Fix missing config dir * Upgrade yq to 4.33.3 2023-04-23 11:35:40 -05:00			`config/*`
			`!config/*.example`
update gitignore 2020-12-14 07:15:59 -06:00			`models`
			`*.mp4`
adding version endpoint 2020-12-19 06:51:10 -06:00			`*.db`
revamp process clip 2021-11-07 14:55:09 -06:00			`*.csv`
feat!: web user interface 2021-01-09 11:26:46 -06:00			`frigate/version.py`
			`web/build`
			`web/node_modules`
test(web): add unit test framework 2021-02-09 13:35:33 -06:00			`web/coverage`
add devcontainer setup 2021-02-17 07:16:39 -06:00			`core`
feat: Timeline UI (#2830) 2022-02-27 08:04:12 -06:00			`!/web/*/.ts`
upgrade to latest openvino version (#11563) 2024-05-27 15:49:35 -05:00			`.idea/*`
			`.ipynb_checkpoints`