Current Slash Commands:

/score This is basically mattybot's equivalent of a hello world command

/get-standings [team_name] Running this returns a table of the current wins and losses. Optionally, you can provide a team name, and then stats will only be shown for that team.

This is our simple (for now) slackbot. If you'd like to contribute, here's how you get started.

After pulling the repo, you'll want to create a venv. Once you've done so, activate it a pip install the requirements.

For slack to be able to communicate with mattybot, we need to be able to verify requests. You'll find secrets.yml.template in the route of this project. Run

cp conf.d/secrets.yml.template conf.d/secrets.yml

and replace the fake values with real ones. Currently this file is a bit bloated and we're only really using the signing_secret but those other values might come in handy later on.

At this point, you're ready to boot up the bot. This can be done by running

DEBUG=True python bot.py

however, you won't be able to do much.

I highly recommend installing ngrok! It'll allow you to expose the flask port to the open web so that the slack API can hit your python process. Once you have it installed, run it in a separate terminal window:

ngrok http 5000

You'll get a forwarding URL which you can set in the slack API UI.

For now, I'm using zappa to automate the lambda deploys, hence the zappa_settings.json. Currently, I'll be the only one doing this, so this next bit is mostly for me. The zappa_settings.json currently only has a dev env so zappa update dev will get the latest code up into AWS.

I can't get over how easy this was. Here are some posts I used to get this up in the cloud and running:

1. Serverless Slash Commands with Python by Renzo Lucioni
   • This post also clued me into ngrok which was super helpful for debugging and testing
2. Verifying Requests from Slack
   • This post by Jani Karhunen was crucial as well, because the first resource uses the old verification system that slack encourages you not to use.