administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-02-09 04:35:25 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update installation.md

Browse Source 
According to the v13 release the config.yml mapping needs to be the entire directory and not only the config.yml file
This commit is contained in:
Florisz 2024-02-24 21:02:56 +01:00 committed by GitHub
parent 6476f8ade7
commit f85a72600e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/frigate/installation.md
View File

@ -240,7 +240,7 @@ There may be other services running on your NAS that are using the same ports th
You need to configure 2 paths:
- The location of your config file in yaml format, this needs to be file and you need to go to the location of where your config.yml is located, this will be different depending on your NAS folder structure e.g. `/docker/frigate/config/config.yml` will mount to `/config/config.yml` within the container.
- The location of your config file in yaml format, this needs to be file and you need to go to the location of where your config.yml is located, this will be different depending on your NAS folder structure e.g. `/docker/frigate/config/config.yml` will mount to `/config/config.yml` within the container. From v13 this mapping needs to be the entire folder instead of specifically the config.yml. So remove the '.yml'. For the example above this would become; `/docker/frigate/config/config' and `/config/config` within the container.
- The location on your NAS where the recordings will be saved this needs to be a folder e.g. `/docker/volumes/frigate-0-media`
![image](https://user-images.githubusercontent.com/4516296/232585872-44431d15-55e0-4004-b78b-1e512702b911.png)