From aea398b5490a2c689ebedf64b4f8b8cb83095377 Mon Sep 17 00:00:00 2001
From: anexas <35750150+anexas@users.noreply.github.com>
Date: Thu, 4 Apr 2024 10:43:35 -0600
Subject: [PATCH] Update pages-and-sections.md

Added additional info for yml files access to Dashy running in docker instance.
---
 docs/pages-and-sections.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/pages-and-sections.md b/docs/pages-and-sections.md
index db70d4b2..6ba22401 100644
--- a/docs/pages-and-sections.md
+++ b/docs/pages-and-sections.md
@@ -22,6 +22,8 @@ pages:
 
 If you're sub-page is located within `/app/public`, then you only need to specify the filename, but if it's anywhere else, then the full path is required.
 
+If you're running Dashy in docker container, then you need to bind mount a local folder to `/app/public` so that Dashy can access the new page config yml file. For example, in docker-compose.yml, define a volume `- ./config:/app/public/pages` to make  local `config/` folder accessible to Dashy at `/app/public/pages/`. You can keep all your config files in this folder where all modifications will be picked up automatically by Dashy. 
+
 ### Using Remote Sub-Pages
 
 Config files don't need to be local, you can store them anywhere, and data will be imported as sub-pages on page load.