make replfor local testing)
!gif dubstep catto test it out
I recommend that you always run limbo in a virtualenv so that you are running in a clean environment.
-t: Enter command line mode to enter a limbo repl.
--hook: Specify the hook to test. (Defaults to "message").
-c: Run a single command.
-d: Where to store the limbo sqlite3 database. Defaults to limbo.sqlite3.
-pp: The path where limbo should look to find its plugins (defaults to /plugins).
-v: Print a version number and exit
Note that if you are getting an error message about not seeing environment variables, you may be running limbo as
sudo, which will clear the environment. Use a virtualenv and always run limbo as a user process!
It's super easy to add your own commands! Just create a python file in the plugins directory with an
on_message function that returns a string.
You can use the
!help command to print out all available commands and a brief help message about them.
!help <plugin> will return just the help for a particular plugin.
By default, plugins won't react to messages from other bots (just messages from humans). Define an
on_bot_message function to handle bot messages too. See the example plugins for an easy way to define these functions.
These are the current default plugins:
make docker_runwill start the default bot.
make docker_stopwill stop the bot
make docker_buildYou'll then need to start the bot with your new_image_name, for example
docker run -d -e SLACK_TOKEN=<your_token> new_image_name