hubot

I’ve written previously about deploying Hubot on Docker, deploying patched Hubot scripts, and bechmarking mass inserts with a Redis Docker container. In this post, I’ll cover how to link a Hubot Docker container to a Redis Docker container to equip Hubot with persistent memory. As an overview we’re going to: Spin up a Redis Docker container with a host directory mounted as a data volume Spin up a linked Hubot Docker container that will use Redis as a persistent brain For my most recent post on Redis mass inserts, I created a basic Redis Docker image that satisfies all of the requirements to be used as a Hubot Redis brain....

In deploying Hubot for the first time, you may encounter the following error: ERROR ReferenceError: fillAddress is not defined at TextListener.callback (/path/to/bot/node_modules/hubot-maps/src/maps.coffee:58:16, <js>:57:18) </truncated> At the time of this writing, running a grep in the Hubot Maps source code shows a single instance of the function and no function definition: grep -rn fillAddress . ./src/maps.coffee:58: location = fillAddress(msg.match[3]) Stepping back a level to grep all of Hubot and scripts yields the same result as above....

A little over a year ago, I wrote a quick blog post about deploying Hubot with Docker. A lot has changed with Hubot and Docker since that time, so I decided to revisit the build. The new implementation I whipped up consists of three main components: Yeoman-generated Hubot Base Docker image Dockerfile for configuring Hubot The Hubot ‘Getting Started’ instructions walk us through generating a deployable Hubot with Yeoman. Once generated, the code can be stashed away somewhere until we’re ready to pull it into a Docker image....

I’ve been playing with Hubot a bit lately, and decided to up the ante on the endeavor by creating a Hubot Docker container. There were a couple of misadventures before landing on a stable source container from which it will now be crazy easy to extend and deploy. I set up Docker using the instructions here. You may notice from reviewing the Dockerfile that line 6 imports a ‘Universe’ apt source....