mirrors/rss-bridge
1
0
Fork 0
mirror of https://github.com/RSS-Bridge/rss-bridge.git synced 2024-11-24 18:36:59 +03:00
Code Issues Projects Releases Packages Wiki Activity

Updated FAQ (markdown)

LogMANOriginal 2018-11-02 09:58:00 +01:00
parent e75ceb11e2
commit 29989dc882
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
FAQ.md

@ -1,14 +1,16 @@
This page provides a collection of frequently asked questions and their answers. Please check this page before opening a new Issue :revolving_hearts: This page provides a collection of frequently asked questions and their answers. Please check this page before opening a new Issue :revolving_hearts:
* [Why is my bridge not showing new contents?](#why-is-my-bridge-not-showing-new-contents) * [Why doesn't my bridge show new contents?](#why-doesnt-my-bridge-show-new-contents)
* [How can I make a bridge update more frequently?](#how-can-i-make-a-bridge-update-more-frequently) * [How can I make a bridge update more frequently?](#how-can-i-make-a-bridge-update-more-frequently)
## Why is my bridge not showing new contents? ## Why doesn't my bridge show new contents?
RSS-Bridge creates a cached version of your contents to reduce the amount of useless traffic. The cached version is created on the first request and served for any subsequent requests. After some time the cached version gets deleted and new content is loaded. The cache duration is bridge specific and can last anywhere between five minutes and 24 hours.
You can specify a custom cache timeout if this option is enabled on the server. See *Customizations* below for more information. RSS-Bridge creates a cached version of your feed in order to reduce traffic and respond faster. The cached version is created on the first request and served for all subsequent requests. On every request RSS-Bridge checks if the cache timeout has elapsed. If the timeout has elapsed, it loads new contents and updates the cached version.
The cache duration is bridge specific and can last anywhere between five minutes and 24 hours. You can specify a custom cache timeout for each bridge if this option has been enabled on the server.
## How can I make a bridge update more frequently? ## How can I make a bridge update more frequently?
You can only do that if you are hosting the RSS-Bridge instance: You can only do that if you are hosting the RSS-Bridge instance:
- Enable `CUSTOM_CACHE_TIMEOUT` on [index.php](https://github.com/RSS-Bridge/rss-bridge/blob/master/index.php#L24); - Enable `CUSTOM_CACHE_TIMEOUT` on [index.php](https://github.com/RSS-Bridge/rss-bridge/blob/master/index.php#L24);
- Eventually, specify the timeout on each bridge by modifying `CACHE_TIMEOUT` constant in the relevant bridge file (e.g [here](https://github.com/RSS-Bridge/rss-bridge/blob/master/index.php#L24) for Twitter). - Eventually, specify the timeout on each bridge by modifying `CACHE_TIMEOUT` constant in the relevant bridge file (e.g [here](https://github.com/RSS-Bridge/rss-bridge/blob/master/index.php#L24) for Twitter).