4 ms·
* I've been running this on heroku for free for weeks. Why would anyone be nervous about that? * As tombell pointed out, you don't need Redis * The docs are o
by cldwalker 15y ago
* I've been running this on heroku for free for weeks. Why would anyone be nervous about that?
* As tombell pointed out, you don't need Redis
* The docs are ok but compared to just ranting docs for this fork they're awesome.
* The docs for IRC usage have moved - https://github.com/nandub/hubot-irc/ https://github.com/nandub/hubot-irc/
* Who cares if Hubot is over-engineered? It has tests. This ranting fork has none. Moving on ...
- IgorPartola 15y agoI would not be running it on Heroku Redis requirement seemed to be strickt based on the docs when Hubot first hit HN Agreed on ranting, but docs are not OK. Docs talk about how awesome it is, but not about how to get it running Those docs were not there AFAIK when it first hit HN. Just because something has unit tests does not mean its paradigm is sound or that it scales or is reliable. This "fork" is not great either by the criteria I use. On top of that both are simply for fun projects not billed as bullet proof battle hardened pieces of software. However, I can see the OP's point of view: Hubot is over-engineered, with a convoluted deploy process outside of Heroku and other design shortcomings. The OP attempted to improve on the idea with a different design, and arguably failed.
- tombell 15y agoIt's actually fairly simple to get running locally, I'll take a look at improving the documentation. 1. Download the latest version from the downloads section 2. Install dependencies with `npm install` 3. Export any environment variables for your adapters and/or scripts 4. `bin/hubot -a <adapter>` That's as simple as it is to run in a terminal. You can use many things to manage the actual process e.g. Foreman/Upstart/Forever.