_________________________________
|.--------_--_------------_--__--.|
|| /\ |_)|_)| /\ | |(_ |_ ||
;;`,_/``\|__|__|__/``\|_| _)|__ ,:|
((_(-,-----------.-.----------.-.)`)
\__ ) ,' `. \ _/
: : |_________| : :
|-'| ,'-.-.--.-.`. |`-|
|_.| (( (* )(* ))) |._|
| | `.-`-'--`-'.' | |
|-'| | ,-.-.-. | |._|
| | |(|-|-|-|)| | |
:,': |_`-'-'-'_| ;`.;
\ \ ,' `. /._/
\/ `._ /_______________\_,' /
\ / : ___________ : \,'
`.| | | | |,'
`.| | | |
Described here.
Extend legion-bot.
TBD: How one actually does this.
Clone one of the templates and go to town.
If it doesn't exist, add it. We need a haskell-bot, for example...
Python supports the concept of "versioning" the distribution--this is stored in the requirements.txt file. If you want to work in a different language or a different version of python, you should add the relevant environment artifacts in the env folder.
Note! Store all unversioned environment artifacts in a folder called src--these are ignored by version control.
Code.
You need to have a startup script in your bots bin directory. That script will be run when the master "init.sh" script is called, so anything your bot needs to have running needs to be spawned in that script.
Add the relevant configuration entries to bot_config.json.
Run init.sh?