From 11ed50074dd64e5d532cf310a150a77f519a4a0e Mon Sep 17 00:00:00 2001 From: Benjamin Brahmer Date: Thu, 1 Oct 2020 16:30:26 +0200 Subject: remove documentation on configuration Signed-off-by: Benjamin Brahmer --- docs/configuration.md | 48 ------------------------------------------------ docs/faq/README.md | 3 +-- 2 files changed, 1 insertion(+), 50 deletions(-) delete mode 100644 docs/configuration.md (limited to 'docs') diff --git a/docs/configuration.md b/docs/configuration.md deleted file mode 100644 index 8c35ce907..000000000 --- a/docs/configuration.md +++ /dev/null @@ -1,48 +0,0 @@ -# Configuration - -The configuration is saved in the database, you can change and view them via the admin interface. - -You can find them in the appconfig table. - -```sql -mysql> select * from oc_appconfig where appid = 'news'; -+-------+--------------------------+-------------+ -| appid | configkey | configvalue | -+-------+--------------------------+-------------+ -| news | autoPurgeCount | 200 | -| news | autoPurgeMinimumInterval | 60 | -| news | enabled | yes | -| news | exploreUrl | | -| news | feedFetcherTimeout | 60 | -| news | installed_version | 15.0.0 | -| news | maxRedirects | 10 | -| news | types | | -| news | updateInterval | 3600 | -| news | useCronUpdates | 1 | -+-------+--------------------------+-------------+ -``` - -# Legacy Configuration before News 15.0.0 - -All configuration values are set inside **nextcloud/data/news/config/config.ini** and can be edited in the admin panel. - -The configuration is in **INI** format and looks like this: - -```ini -autoPurgeMinimumInterval = 60 -autoPurgeCount = 200 -maxRedirects = 10 -maxSize = 104857600 -feedFetcherTimeout = 60 -useCronUpdates = true -exploreUrl = -``` - - -* **autoPurgeMinimumInterval**: Minimum amount of seconds after deleted feeds and folders are removed from the database. Values below 60 seconds are ignored -* **autoPurgeCount**: Defines the maximum amount of articles that can be read per feed which won't be deleted by the cleanup job; if old articles reappear after being read, increase this value; negative values such as -1 will turn this feature off completely -* **maxRedirects**: How many redirects the updater should follow -* **maxSize**: Maximum feed size in bytes. If the RSS/Atom page is bigger than this value, the update will be aborted -* **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 Nextcloud by default by setting this to false -* **exploreUrl**: If given that url will be contacted for fetching content for the explore feed \ No newline at end of file diff --git a/docs/faq/README.md b/docs/faq/README.md index b32ec2c2f..061a351cc 100644 --- a/docs/faq/README.md +++ b/docs/faq/README.md @@ -120,7 +120,6 @@ Check the **nextcloud/data/nextcloud.log** for hints why it failed. After the is Feeds can be updated using Nextcloud's system cron or any program that implements the [News app's updater API](https://github.com/nextcloud/news/tree/master/docs/externalapi), most notably [Nextcloud News Updater](https://github.com/nextcloud/news-updater). **The feed update is not run in Webcron and AJAX cron mode!** System Cron: -* Check if your configuration is set to use the system cron, [check here](https://github.com/nextcloud/news/blob/master/docs/configuration.md). * Check if you are using the system cron (Cron) setting on the admin page. AJAX and Web cron will not update feeds * Check if the cronjob exists with **crontab -u www-data -e** (replace www-data with your httpd user) * Check the file permissions of the **cron.php** file and if **www-data** (or whatever your httpd user is called like) can read and execute that script @@ -143,7 +142,7 @@ System Cron: * If your cron works fine but Nextcloud's cronjobs are never executed, file a bug in [server](https://github.com/nextcloud/server/) [Nextcloud News Updater](https://github.com/nextcloud/news-updater): -* Check if your configuration is set to **not** use the system cron, [check here](https://github.com/nextcloud/news/blob/master/docs/configuration.md). +* Check if your configuration is set to **not** use the system cron. * Start the updater in loglevel info mode and check if the feed update urls are polled, e.g.: nextcloud_news_updater --loglevel info -c /path/to/config.ini -- cgit v1.2.3