No description

Find a file

jesopo 7eb31820d7 Add call_unsafe functions to EventManager.EventHook, to not swallow errors on specific function calls (e.g. preprocess.command)		2018-10-01 16:04:06 +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	Add call_unsafe functions to EventManager.EventHook, to not swallow errors on	2018-10-01 16:04:06 +01:00
src	Add call_unsafe functions to EventManager.EventHook, to not swallow errors on	2018-10-01 16:04:06 +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	received.command takes a final [command] part	2018-09-30 15:07:39 +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 'trace' logging level for src/Database.py and src/EventManager.py very	2018-10-01 13:48:22 +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.)