diff options
author | Candid Dauth <cdauth@cdauth.eu> | 2021-02-20 08:24:53 +0100 |
---|---|---|
committer | Sean Molenaar <SMillerDev@users.noreply.github.com> | 2021-02-20 11:02:38 +0100 |
commit | 78bf8242b38607c114ba1982fde357adbbfc56f5 (patch) | |
tree | 99703a2227e074051c38b9c99f1bd565a859032e /docs | |
parent | d8ce70ff065b289e23c2843c02ac4d384c36b213 (diff) |
Add documentation for manual purging of unread items
Signed-off-by: Candid Dauth <cdauth@cdauth.eu>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/faq/README.md | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/faq/README.md b/docs/faq/README.md index b0a0c025e..ca366910e 100644 --- a/docs/faq/README.md +++ b/docs/faq/README.md @@ -87,3 +87,21 @@ If you do not have control over the chosen feed, you should [download the certif By appending **?subscribe_to=SOME_URL** to your News app URL, you can launch the News app with a pre-filled URL, e.g.: https://yourdomain.com/nextcloud/index.php/apps/news?subscribe_to=https://github.com/nextcloud/news/releases + +### Database table grows too big + +By default, Nextcloud News purges old news items above a certain threshold each time it fetches new news items. The maximum number of items per feed +that should be kept during the purging can be defined through the “Maximum read count per feed” setting in the admin UI or the `autoPurgeCount` +value in the config. (Note: The “Purge interval” (`autoPurgeMinimumInterval`) setting is ignored and does not have any effect.) + +However, unread or starred items are exempt from the purging. If your users have subscribed to some high-volume feeds where a lot of items remain +unread, this can lead to an oversized news table over time. As a consequence, the database upgrade of the news app can take several hours, during which +Nextcloud cannot be used. + +The command `occ news:updater:after-update [--purge-unread] [<purge-count>]` can be used to manually purge old news items across the instance. With +the `--purge-unread` option, unread items are also purged (starred items are still exempt). If `purge-count` is not specifid, the configured +`autoPurgeCount` is used. + +The purge count only applies to the items that are purged. For example, when purging a feed that has 100 unread items, 100 starred read +items and 100 unstarred read items, using a `purge-count` of 50 would keep all unread and starred items and the latest 50 read items. Using +a `purge-count` of 50 along with `--purge-unread` would keep the all starred items plus the latest 50 from the set of unread and read items. |