Stale cache content served after post update – Ghost file‑system cache

Goal: achieve immediate, selective removal of the cached HTML for a specific post when its content is updated via the Ghost admin API, avoiding a full cache flush.

Constraint: Ghost’s file‑system cache under content/data/cache/ is only invalidated by time‑to‑live expiration or by the ghost cache clear command, which deletes the entire cache directory and can cause load spikes on high‑traffic sites.

Uncertainty: the documentation notes the lack of a built‑in selective cache‑invalidation webhook or configuration option, leaving administrators to rely on TTL or manual full purges.

Questions: Is there a supported method to trigger deletion of the individual cache file for a updated post through the admin API or a webhook? Can the cache TTL be set per‑route or per‑post to achieve faster invalidation without a full flush? Are there any upcoming features or community plugins that provide selective cache purging for Ghost?