[GH-ISSUE #590] Support for password-file in subscribe entries in client.yml #449

Closed
opened 2026-05-07 00:24:17 +02:00 by BreizhHardware · 2 comments

Originally created by @arjan-s on GitHub (Jan 19, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/590

I would like to request support for a password-file option next to the existing password option inside the subscribe option in client.yml. The reason for requesting this is that I use agenix for handling my serverside secrets, and as such I can't hardcode passwords in config files. The password for a ntfy subscription could for instance be published in /run/agenix/ntfy_topic_pw, and I would like ntfy to be able to read it from there.

Originally created by @arjan-s on GitHub (Jan 19, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/590 I would like to request support for a `password-file` option next to the existing `password` option inside the `subscribe` option in `client.yml`. The reason for requesting this is that I use [agenix](https://github.com/ryantm/agenix) for handling my serverside secrets, and as such I can't hardcode passwords in config files. The password for a ntfy subscription could for instance be published in `/run/agenix/ntfy_topic_pw`, and I would like ntfy to be able to read it from there.
BreizhHardware 2026-05-07 00:24:17 +02:00
Author
Owner

@arjan-s commented on GitHub (Jan 21, 2023):

I solved this by assigning $NTFY_USER using EnvironmentFile in my systemd service. The approach suggested in this issue still has my preference, but at least it works now. :)

<!-- gh-comment-id:1399319656 --> @arjan-s commented on GitHub (Jan 21, 2023): I solved this by assigning `$NTFY_USER` using `EnvironmentFile` in my systemd service. The approach suggested in this issue still has my preference, but at least it works now. :)
Author
Owner

@binwiederhier commented on GitHub (Feb 2, 2026):

Similar to this ticket (https://github.com/binwiederhier/ntfy/issues/1492), I don't really want to support this. The config file can easily be made private.

<!-- gh-comment-id:3832536610 --> @binwiederhier commented on GitHub (Feb 2, 2026): Similar to this ticket (https://github.com/binwiederhier/ntfy/issues/1492), I don't really want to support this. The config file can easily be made private.
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#449
No description provided.