c/ntfy · by loving_ntfy@lemm.ee · 2y

message-expiry-duration vs cache-duration config options

What is the difference between the two.

The cache-duration is explained in the docs and is fairly clear:

Duration for which messages will be buffered before they are deleted

so it is to account for network interruptions of subscribers.

message-expiry-duration is mentioned but there is no explanation for it in the docs.

2 points · 2 comments · view on lemmy.world

2 Comments

binwiederhier@discuss.ntfy.sh · 1 pts · 2y (1 reply)

--message-expiry-duration is an option that you can pass when creating a new tier (in your selfhosted instance). It is equivalent to the cache-duration for users publishing in that tier.

For instance, if you are a ntfy Pro user, your messages are cached much longer than the normal 12h (see https://ntfy.sh/v1/tiers).

The naming is a little odd. I think cache-duration should probably be called something else.

loving_ntfy@lemm.ee · 2 pts · 2y

Not quite clear.

Given I have no tiers, I am covered just with cache-duration and can completely ignore message-expiry-duration?

I have a single service that POSTs messages to ntfy which sends them to subscribers. Any subscriber will have to connect within cache-duration or else ntfy deletes messages older than that from the database. Is that accurate? The intention is to keep the sqlite db lean and small.