Firepup650/bitbot-3.11-fork
2
0
Fork 0
Code Issues Pull requests Activity Actions
No description
1023 commits 2 branches 0 tags 4.4 MiB
Python 100%
Find a file
jesopo dda60ae417 _give_from_pool/_take_from_pool take a server argument
2018-10-12 16:27:59 +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 _give_from_pool/_take_from_pool take a server argument 2018-10-12 16:27:59 +01:00
src Use decimal.Decimal in utils.parse_number 2018-10-12 11:28:14 +01:00
.gitignore Remove unneeded things from .gitignore 2018-09-24 15:44:31 +01:00
bot.conf.example Remvoe 'control-socket' from bot.conf.example 2018-10-07 08:04:25 +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 Add requests to README.md dependencies 2018-10-10 14:43:44 +01:00
requirements.txt Change utils.http to use requests 2018-10-10 13:41:58 +01:00
start.py Fix start.py not giving the right arguments to database.servers.add 2018-10-03 16:00:25 +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.)