README.md: Minor improvements

This commit is contained in:
Albert S. 2020-08-19 19:43:06 +02:00 committed by Albert S
parent 7667d32191
commit 6a9849fe09
1 changed files with 6 additions and 1 deletions

View File

@ -16,7 +16,7 @@ like google's feed proxy and cloudflare. They may identify you across
devices as it is very likely that the combination of feeds you read devices as it is very likely that the combination of feeds you read
is unique. In the context of "hardening", this is also useful to is unique. In the context of "hardening", this is also useful to
restrict the servers your RSS client can contact (for instance, restrict the servers your RSS client can contact (for instance,
by using network namespaces, etc.). by using network namespaces or [qsni](https://gitea.quitesimple.org/crtxcr/qsni)).
A drawback of this approach is that the time you get new feeds A drawback of this approach is that the time you get new feeds
is delayed, but that should be acceptable. Furthermore, this tool is delayed, but that should be acceptable. Furthermore, this tool
@ -38,12 +38,17 @@ For each feed, an individual config file is used.
Example: Example:
A simple example config file for kernel.org: A simple example config file for kernel.org:
```
FEED_URL="https://www.kernel.org/feeds/kdist.xml" FEED_URL="https://www.kernel.org/feeds/kdist.xml"
FEED_OUTPUT="/var/www/feeds/kernelreleases.feed" FEED_OUTPUT="/var/www/feeds/kernelreleases.feed"
```
Launch Launch
------ ------
```
randrss [path to directory containing the config files] [fetchersfile] randrss [path to directory containing the config files] [fetchersfile]
```
fetchersfile: take a look at the example file in the repo. It lists fetchersfile: take a look at the example file in the repo. It lists
the paths to the fetchers that will randomly be used. the paths to the fetchers that will randomly be used.