[GH-ISSUE #1214] Topic-specific Configurations #857

Open
opened 2026-05-05 04:20:14 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @tentme on GitHub (Nov 3, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1214

💡 Idea

As the title suggests, this will allow admin to specify custom attachment size limits, expiration times, etc. for individual topics.

For example, via server.yml:

topics:
  my_topic:
    attachment-file-size-limit: 20MB
    attachment-expiry-duration: 12h
  another_topic:
    attachment-file-size-limit: 5MB
    attachment-expiry-duration: 1h

Or, like auth-file, these configurations could be put into a .db file and modified dynamically via the ntfy CLI.

I imagine this could provide more flexibility and better resource management. And it would cool if this implemented like Tiers.

Originally created by @tentme on GitHub (Nov 3, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1214 :bulb: **Idea** As the title suggests, this will allow admin to specify custom attachment size limits, expiration times, etc. for individual topics. For example, via `server.yml`: ```yaml topics: my_topic: attachment-file-size-limit: 20MB attachment-expiry-duration: 12h another_topic: attachment-file-size-limit: 5MB attachment-expiry-duration: 1h ``` Or, like `auth-file`, these configurations could be put into a `.db` file and modified dynamically via the ntfy CLI. I imagine this could provide more flexibility and better resource management. And it would cool if this implemented like **Tiers**.
gitea-mirror added the
enhancement
label 2026-05-05 04:20:14 -06:00
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: github-starred/ntfy#857
No description provided.