Nessuna descrizione http://bits.zero9f9.com/pybot
Matt Weller 42d69e372f Merge branch 'master' into TSDBotFeatures | 9 anni fa | |
---|---|---|
docs | 9 anni fa | |
modules | 9 anni fa | |
tests | 9 anni fa | |
.gitignore | 10 anni fa | |
.travis.yml | 10 anni fa | |
CHANGES | 10 anni fa | |
README.md | 9 anni fa | |
Vagrantfile | 10 anni fa | |
bootstrap.sh | 10 anni fa | |
bot.py | 9 anni fa | |
botbrain.py | 9 anni fa | |
conferror.py | 11 anni fa | |
confman.py | 10 anni fa | |
db.py | 9 anni fa | |
event.py | 9 anni fa | |
lite.py | 10 anni fa | |
logger.py | 9 anni fa | |
mysql_dump | 10 anni fa | |
pybotrc | 9 anni fa | |
requirements.txt | 9 anni fa | |
run.sh | 9 anni fa | |
setup.sh | 10 anni fa | |
stats.py | 11 anni fa | |
ubuntu.sh | 10 anni fa | |
util.py | 10 anni fa | |
version.py | 9 anni fa | |
webwriter.py | 10 anni fa |
he is modular, extensible, multi-threaded, and configurable.
pybot runs on python 2.6 and 2.7, on both windows and linux.
python versions > 3 are in the works.
cp pybotrc ~/.pybotrc
)./bot.py
./bot.py -d.
sudo ./bootstrap.sh
to install pybot dependencies such as mysql../setup.sh
. It will check for module dependencies and create a mysql_init file. mysql -p < mysql_init
./bot.py pybotrc
./bot.py -d.
Add a mysql user for pybot with permissions to update, insert, and delete from the created tables.
Logged into mysql: grant all on <dbname>.* to '<username>' identified by '<password>';
Run the included mysql_dump file (as root, mysql -p <pybot's database name> < mysql_dump
).
Set his dbpass in the config file (pybotrc) to the password you've given him.
Copy that config file to the home folder of whatever user will be running the bot. (~user/.pybotrc)
As that user, ./bot.py.
If you have Vagrant locally installed and configured, you can set up pybot by invoking
vagrant up
. Your development environment will be configured, and you can skip step 1 and
2 above. After that, SSH into your VM and do steps 3 through 5 to finish things off.
Here pybot is connected to two networks at once. They are held entirely separately. Modules loaded on one are independent of modules loaded on another. If one server goes down, the other connections to other networks are unaffected.