No description
Find a file
2018-08-31 17:07:08 +01:00
modules THE OVERLORD DEMANDS I TRASH IT 2018-08-31 17:04:15 +01:00
.gitignore Added rotated log files to gitignore 2018-08-08 20:24:51 +01:00
bot.conf.example switch to using configparser for config files 2018-07-16 00:36:52 +01:00
Config.py Return config from Config.load_config instead of setting it on bot 2018-08-30 11:40:41 +01:00
Database.py Update Database.py 2018-08-31 16:10:16 +01:00
EventManager.py Support replay keyword in EventHookContext.hook 2018-08-31 13:44:39 +01:00
IRCBot.py Give modules event objects with "context"s, to facilitate purging all the event 2018-08-31 13:44:39 +01:00
IRCBuffer.py Forgot to add IRCBuffer.py when I renamed it from IRCLog.py. oops. 2018-08-29 12:55:20 +01:00
IRCChannel.py Add Database.UserChannelSettings.find_all_by_setting 2018-08-31 15:18:59 +01:00
IRCLineHandler.py Some networks don't prefix channel names in INVITE messages 2018-08-31 13:44:39 +01:00
IRCLogging.py Log exceptions when calling events 2018-08-30 14:56:27 +01:00
IRCServer.py All the settings (#11) 2018-08-31 15:49:57 +01:00
IRCUser.py All the settings (#11) 2018-08-31 15:49:57 +01:00
LICENSE Initial commit 2016-03-29 12:44:46 +01:00
ModuleManager.py Give modules event objects with "context"s, to facilitate purging all the event 2018-08-31 13:44:39 +01:00
README.md switch to using configparser for config files 2018-07-16 00:36:52 +01:00
start.py Give modules event objects with "context"s, to facilitate purging all the event 2018-08-31 13:44:39 +01:00
Timer.py Give modules event objects with "context"s, to facilitate purging all the event 2018-08-31 13:44:39 +01:00
Utils.py Only show 2 biggest units in !seen 2018-08-29 15:52:04 +01:00

BitBot

Python3 event-driven modular IRC bot!

Dependencies

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

Data storage

The main data storage for Bitbot is done in his sqlite3 database, bot.db.