Firepup650/bitbot-3.11-fork
2
0
Fork 0
Code Issues Pull requests Activity Actions
No description
836 commits 2 branches 0 tags 4.4 MiB
Python 100%
Find a file
jesopo 8f2f1b43f2 Make section headers ## instead of ###
2018-09-30 11:59:37 +01:00
databases Move log and database files to their own folders 2018-09-24 15:26:31 +01:00
logs Move log and database files to their own folders 2018-09-24 15:26:31 +01:00
modules We don't need to explicitly pass "buffer" through on command events 2018-09-30 11:43:34 +01:00
src Use a zero-width non-joiner to prevent highlights, instead of a zero-width 2018-09-29 15:57:15 +01:00
.gitignore Remove unneeded things from .gitignore 2018-09-24 15:44:31 +01:00
bot.conf.example Comment config options! 2018-09-26 11:21:24 +01:00
EVENTS.md Make section headers ## instead of ### 2018-09-30 11:59:37 +01:00
LICENSE Initial commit 2016-03-29 12:44:46 +01:00
README.md Remove unneeded Data Storage section of README.md 2018-09-26 18:27:39 +01:00
requirements.txt Add requirements.txt 2018-09-24 15:36:17 +01:00
start.py Add src/Cache.py, use it in modules/coins.py 2018-09-29 12:53:39 +01:00

README.md

BitBot

Python3 event-driven modular IRC bot!

Dependencies

Use pip3 install -r requirements.txt to install them all at once.

Configurating

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.)

Eagle

BitBot's National Rail module can optionally include output from Network Rail's SCHEDULE via Eagle. Configuration on BitBot's end is covered by the eagle- keys in bot.conf.example.

Running

Just run ./start.py

On first boot, he'll ask for a first server to connect to then exit. do ./start.py again and he'll connect to that server and join #bitbot (to get him to join other channels, simply invite him to them.)