'info' -> 'information' (README.md)
This commit is contained in:
parent
43b50e37b3
commit
3b263aab2c
1 changed files with 1 additions and 1 deletions
|
@ -15,7 +15,7 @@ Use `pip3 install -r requirements.txt` to install them all at once.
|
||||||
To get BitBot off the ground, there's some API-keys and the like in bot.conf.example. move it to bot.conf, fill in the API keys you want (and remove the ones you don't want - this will automatically disable the modules that rely on them.)
|
To get BitBot off the ground, there's some API-keys and the like in bot.conf.example. move it to bot.conf, fill in the API keys you want (and remove the ones you don't want - this will automatically disable the modules that rely on them.)
|
||||||
|
|
||||||
## Github web hooks
|
## Github web hooks
|
||||||
I run BitBot as-a-serivce on most popular network and offer github-to-IRC web hook notifications for free to FOSS projects. Contact me for more info!
|
I run BitBot as-a-serivce on most popular network and offer github-to-IRC web hook notifications for free to FOSS projects. Contact me for more information!
|
||||||
|
|
||||||
## Eagle
|
## Eagle
|
||||||
BitBot's National Rail module can optionally include output from Network Rail's SCHEDULE via [Eagle](https://github.com/EvelynSubarrow/Eagle). Configuration on BitBot's end is covered by the `eagle-` keys in bot.conf.example.
|
BitBot's National Rail module can optionally include output from Network Rail's SCHEDULE via [Eagle](https://github.com/EvelynSubarrow/Eagle). Configuration on BitBot's end is covered by the `eagle-` keys in bot.conf.example.
|
||||||
|
|
Loading…
Reference in a new issue