mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #302] [QUESTION] whoogle.env on Synology #208
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Chris122AT on GitHub (May 1, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/302
Hi there,
how can I use the file whoogle.env persistant on a Synology NAS?
I tried to set -v [volumeX/path_to/]whoogle.env:/whoogle.env and set -e WHOOGLE_DOTENV=1.
So the file should be mounted. But after docker start whoogle it doesn't affects whoogle's configuration.
Thank you for your help!
Chris
@benbusby commented on GitHub (May 3, 2021):
It's probably better to just use
--env-file ./whoogle.env(or-e ./whoogle.env) to load thewhoogle.envfile.That should work better than mounting directly, but let me know if you are still encountering any problems with that approach!
@Chris122AT commented on GitHub (May 5, 2021):
@benbusby
Hello Ben,
I edited the whoogle.env in the container and as long as the container is running everything is fine. The problem is that after each update (by Watchtower) the whoogle.env is overwritten from the new image. That's why I would take the whoogle.env persistent to the Synology DSM file system.
I have never had any problems with the mounting of docker containers. In principle, I can not understand why the mount does not work.
Thank you for your efforts!
Chris