Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUESTION] How to get automatic files refreshing with docker compose deployment ? #1824

Open
4 tasks done
maks7d opened this issue Mar 9, 2025 · 0 comments
Open
4 tasks done
Assignees
Labels
🤷‍♂️ Question [ISSUE] Further information is requested

Comments

@maks7d
Copy link

maks7d commented Mar 9, 2025

Question

I deployed dashy on my server using docker compose. I made my own widget which scans the connected users to my VPN. For that, I use an html page which reads in a .json file where all the connected users are stored. This .json is refreshed every 5 minutes. The issue is dashy isn't refreshing automatically the html file to refresh the widget. I must docker compose down then docker compose up -d to update the connected users and any modification in my html file. For the config.yml file, I mounted a volume to refresh automatically the configuration of the page and this works by linking my config.yml to /app/user-data/conf.yml. I tried to do the same for my html file by mounting a volume in /app/public but it doesn't work. My question is : how to get dashy refreshing automatically some files we have selected placed in a certain folder ? I didn't any answer to that question with docker compose in the documentation, neither in the issues, nor in chatgpt. Thanks.

Here is the docker-compose.yml file I use :
docker-compose.txt

Category

Setup and Deployment

Please tick the boxes

@maks7d maks7d added the 🤷‍♂️ Question [ISSUE] Further information is requested label Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷‍♂️ Question [ISSUE] Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants