message-expiry-duration vs cache-duration config options
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.
You're viewing a single thread.
--message-expiry-durationis an option that you can pass when creating a new tier (in your selfhosted instance). It is equivalent to thecache-durationfor 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-durationshould probably be called something else.Not quite clear.
Given I have no tiers, I am covered just with
cache-durationand can completely ignoremessage-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-durationor else ntfy deletes messages older than that from the database. Is that accurate? The intention is to keep the sqlite db lean and small.