diff options
| author | Bernhard Posselt <Raydiation@users.noreply.github.com> | 2013-09-10 15:39:23 +0200 |
|---|---|---|
| committer | Bernhard Posselt <Raydiation@users.noreply.github.com> | 2013-09-10 15:39:23 +0200 |
| commit | 7d31b78dd03ae4747973be2d5bc9c5a7eedafea2 (patch) | |
| tree | bade83d878286198c234a973282a329adf3d7c16 | |
| parent | b47f0dee5e39df154db65feb92b2f3ae58d9ec24 (diff) | |
Update README.rst
| -rw-r--r-- | README.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/README.rst b/README.rst index ab6f2bb5b..5e8c7c0c7 100644 --- a/README.rst +++ b/README.rst @@ -173,7 +173,7 @@ The configuration is in **INI** format and looks like this: * **autoPurgeMinimumInterval**: Minimum amount of seconds after deleted feeds and folders are removed from the database. -* **autoPurgeCount**: To let people have more read and unstarred items per feed before they are purged increase this value +* **autoPurgeCount**: To let people have more read and unstarred items per feed before they are deleted increase this value. If you set this too low this will cause read articles to reappear: For instance a feed offers the newest 100 entries. The user reads 80 of them, the autoPrugeCount is set to 20. After the cleanup which runs with the update only 20 read entries of that feed will remain, which means 60 entries are deleted. The next update will then readd those 60 entries because they are gone from the database and thus appear to be new entries. * **simplePieCacheDuration**: Amount of seconds to cache feeds * **feedFetcherTimeout**: Maximum number of seconds to wait for an RSS or Atom feed to load. If a feed takes longer than that number of seconds to update, the update will be aborted * **useCronUpdates**: To use a custom update/cron script you need to disable the cronjob which is run by ownCloud by default by setting this to false |