[Domenic_S]

I love the tech, but hate how heroku-centric it all is. If you want to spin up your own hubot+heaven instance somewhere not-heroku, glhf.

[listenrightmeow]

https://github.com/listenrightmeow/dbot

http://pgarbe.github.io/blog/2015/03/24/how-to-run-hubot-in-...

There are a couple articles/repos out there with detailed steps on running Hubot on AWS. While the ease and simplicity of deploying Hubot outside of Heroku is not a tenth as easy, there are a couple of options out there.

[Domenic_S]

I guess I'm lazy and want an apt-get/yum/brew recipe. What if I have to install it on iron behind a corporate firewall?

[davewongillies]

Then you just follow the installation instructions on your iron behind your corporate firewall: https://hubot.github.com/docs/

My team controls our hubots on iron behind a firewall with hubot-control, which can also create hubots for you too: https://github.com/spajus/hubot-control

[Domenic_S]

Right, but then you need some kind of deployment adaptor to do something useful (like deploying apps) -- Heaven's the recommended one, but

> Heaven is a rails app that was designed to be hosted on heroku. https://github.com/atmos/heaven/blob/master/doc/installation...

Now we've got dependencies on node, npm, ruby, rails, heroku, some datastore, a queue for hubot, whatever your actual builder is (capistrano/chef/whatever) etc etc.

Right now I do all this with Jenkins+bash scripts. Inelegant and not as robust as I'd prefer, but so simple. I could just use a Jenkins adaptor for hubot, but then what's the point? I want locking environments, advanced permissions, and so forth.

I'm mostly complaining because I'm dying to implement chatops (mostly for slack-based deployments) but the information is really light, or the tools are too environment-specific, and I don't have people to bounce ideas/questions off of.

[jarek]

There's always Supybot which runs basically anywhere :)