Firepup650/bitbot-3.11-fork
2
0
Fork 0
Code Issues Pull requests Activity Actions
No description
561 commits 2 branches 0 tags 4.4 MiB
Python 100%
Find a file
jesopo 06a750edbd Remove channel from autojoin when BitBot parts it
2018-09-03 12:22:06 +01:00
modules Remove channel from autojoin when BitBot parts it 2018-09-03 12:22:06 +01:00
.gitignore Added rotated log files to gitignore 2018-08-08 20:24:51 +01:00
bot.conf.example Add virustotal-api-key to bot.conf.example 2018-09-02 18:39:31 +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 Table name typo 2018-08-31 16:02:48 +01:00
EventManager.py Don't purge children on purge_context() in EventHook, make event_context 2018-09-01 18:27:10 +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 give an Exports object (actually, ExportsContex object) to each module, to 2018-09-02 19:54:45 +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:13:56 +01:00
IRCLineHandler.py typo! targer -> target 2018-09-03 12:16:27 +01:00
IRCServer.py Support IRCv3's chghost and invite-notify 2018-09-03 11:47:11 +01:00
IRCUser.py Actually, we do need find_all_by_setting 2018-08-31 15:34:56 +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 12:55:52 +01:00
Timer.py Give modules event objects with "context"s, to facilitate purging all the event 2018-08-31 12:55:52 +01:00
Utils.py Add Utils.bold and Utils.underline 2018-09-01 10:34:55 +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.