chylex/Nextcloud-News
1
0
Fork 0
mirror of https://github.com/chylex/Nextcloud-News.git synced 2025-04-26 14:15:48 +02:00
Code

remove documentation on configuration

Browse Source 
Signed-off-by: Benjamin Brahmer <info@b-brahmer.de>
This commit is contained in:
Benjamin Brahmer 2020-10-01 16:30:26 +02:00 committed by Sean Molenaar
parent e1426bfa50
commit 11ed50074d
3 changed files with 3 additions and 52 deletions

4
README.md
View File

@ -6,8 +6,8 @@
The News app is an RSS/Atom feed aggregator. It offers a [RESTful API](https://github.com/nextcloud/news/tree/master/docs/externalapi/Legacy.md) for app developers. The source code is [available on GitHub](https://github.com/nextcloud/news)
## Install and configuration
See the [install document](https://github.com/nextcloud/news/blob/master/docs/install.md) and the [configuration overview](https://github.com/nextcloud/news/blob/master/docs/configuration.md)
## Install
See the [install document](https://github.com/nextcloud/news/blob/master/docs/install.md)
## FAQ
* [My browser shows a mixed content warning](https://github.com/nextcloud/news/blob/master/docs/faq/README.md#my-browser-shows-a-mixed-content-warning-connection-is-not-secure)

48
docs/configuration.md
View File

@ -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

3
docs/faq/README.md
View File

@ -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