From f85a72600ec58deaeb5bd9b9f35d6ab6b9294bfa Mon Sep 17 00:00:00 2001 From: Florisz <19168937+Floriszz@users.noreply.github.com> Date: Sat, 24 Feb 2024 21:02:56 +0100 Subject: [PATCH] Update installation.md According to the v13 release the config.yml mapping needs to be the entire directory and not only the config.yml file --- docs/docs/frigate/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/frigate/installation.md b/docs/docs/frigate/installation.md index 99565acf8..3c7a58603 100644 --- a/docs/docs/frigate/installation.md +++ b/docs/docs/frigate/installation.md @@ -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)