[GH-ISSUE #325] Self-hosted docker - setting.yaml not being loaded? #254

Closed
opened 2026-05-07 00:22:20 +02:00 by BreizhHardware · 2 comments

Originally created by @milksteakjellybeans on GitHub (Jun 11, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/325

When using the self-hosted docker image, the settings.yaml does not seem to get loaded. Here's a simple example,

docker run based on simplified docker example from https://ntfy.sh/docs/install/#docker

$ cat run_ntfy_ex2.sh
docker run \
  -v /home/dude/d_ntfy/ex/etc/ntfy:/etc/ntfy \
  -p 80:80 \
  -it \
  binwiederhier/ntfy:v1.25.2 \
  serve

simple settings.yaml

$ cat /home/dude/d_ntfy/ex/etc/ntfy/server.yaml 
# Log level, can be TRACE, DEBUG, INFO, WARN or ERROR
# This option can be hot-reloaded by calling "kill -HUP $pid" or "systemctl reload ntfy".
#
# Be aware that DEBUG (and particularly TRACE) can be VERY CHATTY. Only turn them on for
# debugging purposes, or your disk will fill up quickly.
#
log-level: DEBUG

output:

# sh run_ntfy_ex2.sh 
2022/06/11 20:57:29 INFO Listening on :80[http], log level is INFO

Note the log level

Maybe this is a permissions requirement that I do not understand.

Thank you

Originally created by @milksteakjellybeans on GitHub (Jun 11, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/325 When using the self-hosted docker image, the settings.yaml does not seem to get loaded. Here's a simple example, docker run based on simplified docker example from https://ntfy.sh/docs/install/#docker ``` $ cat run_ntfy_ex2.sh docker run \ -v /home/dude/d_ntfy/ex/etc/ntfy:/etc/ntfy \ -p 80:80 \ -it \ binwiederhier/ntfy:v1.25.2 \ serve ``` simple settings.yaml ``` $ cat /home/dude/d_ntfy/ex/etc/ntfy/server.yaml # Log level, can be TRACE, DEBUG, INFO, WARN or ERROR # This option can be hot-reloaded by calling "kill -HUP $pid" or "systemctl reload ntfy". # # Be aware that DEBUG (and particularly TRACE) can be VERY CHATTY. Only turn them on for # debugging purposes, or your disk will fill up quickly. # log-level: DEBUG ``` output: ``` # sh run_ntfy_ex2.sh 2022/06/11 20:57:29 INFO Listening on :80[http], log level is INFO ``` Note the log level Maybe this is a permissions requirement that I do not understand. Thank you
Author
Owner

@binwiederhier commented on GitHub (Jun 11, 2022):

It's server.yml, not server.yaml. :-)

<!-- gh-comment-id:1153019240 --> @binwiederhier commented on GitHub (Jun 11, 2022): It's server.yml, not server.yaml. :-)
Author
Owner

@milksteakjellybeans commented on GitHub (Jun 12, 2022):

whoopsie-doodle.yaml, thank you for reviewing

<!-- gh-comment-id:1153038881 --> @milksteakjellybeans commented on GitHub (Jun 12, 2022): whoopsie-doodle.yaml, thank you for reviewing
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#254
No description provided.