| # Description | |
| # Hubot, you complete me | |
| # | |
| # Commands: | |
| # hubot complete me - Google Suggest a phrase | |
| XMLJS = require "xml2js" | |
| module.exports = (robot) -> | |
| robot.respond /complete( me)?(?: x(\d+))? (.*)$/i, (msg) -> |
vet: Hey Kevin will you be there for camp build?
kevin: Ohh naw bro, I'm coming in Burner Express, sorry.
vet: Ok, but you'll be there to help tear down camp?
kevin: Ohh nope sorry, Expressing out Sunday at 9a brah.
vet: Ok... can you bring some extra water or food for your campmates?
@holman got a request about our deployment system, heaven
I know it's not a high priority, but has there been any activity on open-sourcing the core Heaven gem?
There is. I've been working on extracting the non-GitHub specific parts into two gems. This first is a CLI portion called hades. The second is an HTTP API portion called heaven.
When you open source something previously used as in internal tool like Heaven, Hubot, Boxen, etc., how do you manage and hook in the parts that need to stay internal?
Normally I focus around four questions:
| require 'pp' | |
| require 'sinatra/auth/github' | |
| module Signup | |
| def self.app | |
| @app ||= Rack::Builder.new do | |
| use Rack::Static, :urls => ["/stylesheets", "/images", "/javascripts"], :root => "public" | |
| run Signup::App | |
| end |
