No description

Find a file

Evelyn aaca9dc4a6 Quit: We're getting there		2018-12-20 23:45:30 +00: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	Quit: We're getting there	2018-12-20 23:45:30 +00:00
src	Typo, '=' -> '==' (utils.irc)	2018-12-12 11:50:59 +00:00
.gitignore	Change .gitignore entry for log files to include new 'trace.log'/'warn.log'	2018-11-27 12:00:31 +00:00
bot.conf.example	Add 'bot-channel' config in bot.conf.example and use it, if present, in	2018-12-06 12:13:59 +00: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 telegram functionality - it's very broken/outdated and needs a	2018-12-05 15:53:49 +00:00
requirements.txt	Remove telegram functionality - it's very broken/outdated and needs a	2018-12-05 15:53:49 +00:00
start.py	Log any unhandled (critical) exceptions that happen under `bot.run()` in	2018-11-26 14:07:01 +00: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.)

Contact/Support

Come say hi at ##bitbot on freenode