Firepup650/bitbot-3.11-fork
2
0
Fork 0
Code Issues Pull requests Activity Actions
No description
699 commits 2 branches 0 tags 4.4 MiB
Python 100%
Find a file
jesopo a8bf248d47 Fix copypaste fail in Utils that meant we had no RFC1459_LOWER
2018-09-11 10:14:37 +01:00
modules Typo, event["server"] -> server 2018-09-10 08:58:15 +01:00
.gitignore Add database_backup.py for rotated database backups 2018-09-03 18:20:53 +01:00
bot.conf.example bitly-api-key isn't used anymore 2018-09-09 22:02:40 +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 Change default priority to "medium", add priority lower than "low" ("monitor") 2018-09-09 17:08:38 +01:00
Exports.py give an Exports object (actually, ExportsContex object) to each module, to 2018-09-02 19:54:45 +01:00
IRCBot.py Debug log raw data 2018-09-04 07:20:17 +01:00
IRCBuffer.py Respect RFC1459 casemapping rules 2018-09-11 08:52:12 +01:00
IRCChannel.py Respect RFC1459 casemapping rules 2018-09-11 08:52:12 +01:00
IRCLineHandler.py Respect RFC1459 casemapping rules 2018-09-11 08:52:12 +01:00
IRCServer.py Forgot to import Utils in IRCServer 2018-09-11 10:14:12 +01:00
IRCUser.py Respect RFC1459 casemapping rules 2018-09-11 08:52:12 +01:00
LICENSE Initial commit 2016-03-29 12:44:46 +01:00
Logging.py IRCLogging -> Logging 2018-09-02 19:52:18 +01:00
ModuleManager.py give an Exports object (actually, ExportsContex object) to each module, to 2018-09-02 19:54:45 +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 Fix copypaste fail in Utils that meant we had no RFC1459_LOWER 2018-09-11 10:14:37 +01:00

README.md

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.