4 ms·

News just in: cool and fun side project doesn't do things the 'serious' way. Hubot doesn't "require" Redis, don't load the `redis-brain.coffee` script. Problem

by tombell 15y ago

News just in: cool and fun side project doesn't do things the 'serious' way. Hubot doesn't "require" Redis, don't load the `redis-brain.coffee` script. Problem solved. Hubot is a framework for building your own useful things on top of it. Sure it doesn't provide a billion and one ways to do useful thing, you add those yourself. If it doesn't work for you, don't use it simple as. Given it is a fun side project a company can use, I don't think the concept of "production" or "development" comes into it. You just run it. Plenty of people have run it without issues, and anyone that have had issues has been helped to have them resolved. Feel free to send a pull request to improve documentation rather than just slate it :). Hubot is what YOU make it, not what you can just download and hope it brings useful things to your team.

IgorPartola 15y ago
I understand that Hubot is more framework than finished product. My point is that when I am evaluating whether to implement it fir the company I work for vs spending time and resources on some other side project, I am having a hard time making a case for this particular framework. As for production vs dev: Hubit is either your tool for deploying code or it is not. If there are many ways to deploy the same piece of code you are doing it wrong. Now consider being the Ops guy who has to deploy a critical security fix and Hubot took a cigarette break because it never started properly or some other bug in the code caused it to fail.
- tombell 15y ago
  Understandable. But surely you would have a fall back way to deploy given your main way doesn't work? I can deploy my apps via Hubot, but I can also deploy them without Hubot because I have an abstraction that Hubot uses to deploy my apps. And as far as I know GitHub have also something similar in place. A bug in any piece of software is going to cause issues, Hubot isn't an exception.
  - IgorPartola 15y ago
    Yes. And I agree that any piece of software in you stack can ahve bugs that make life difficult. My issue is that (1) Hubot is supposed to be central to your ecosystem and (2) when I looked at the code at first I saw a style of deployment and docs that made me think that running it would be more trouble than it's worth.
    - tombell 15y ago
      I am continually trying to help improve the deployment and documentation of Hubot, and I even created https://hubot-factory.herokuapp.com https://hubot-factory.herokuapp.com that makes it really easy to get up and running on Heroku.
      - IgorPartola 15y ago
        Cool. That's good to know. FWIW, this is the kind of project I would contribute to, was my plant not so full currently.

by tombell 15y ago

IgorPartola 15y ago

I understand that Hubot is more framework than finished product. My point is that when I am evaluating whether to implement it fir the company I work for vs spending time and resources on some other side project, I am having a hard time making a case for this particular framework. As for production vs dev: Hubit is either your tool for deploying code or it is not. If there are many ways to deploy the same piece of code you are doing it wrong. Now consider being the Ops guy who has to deploy a critical security fix and Hubot took a cigarette break because it never started properly or some other bug in the code caused it to fail.

tombell 15y ago
Understandable. But surely you would have a fall back way to deploy given your main way doesn't work? I can deploy my apps via Hubot, but I can also deploy them without Hubot because I have an abstraction that Hubot uses to deploy my apps. And as far as I know GitHub have also something similar in place. A bug in any piece of software is going to cause issues, Hubot isn't an exception.
- IgorPartola 15y ago
  Yes. And I agree that any piece of software in you stack can ahve bugs that make life difficult. My issue is that (1) Hubot is supposed to be central to your ecosystem and (2) when I looked at the code at first I saw a style of deployment and docs that made me think that running it would be more trouble than it's worth.
  - tombell 15y ago
    I am continually trying to help improve the deployment and documentation of Hubot, and I even created https://hubot-factory.herokuapp.com https://hubot-factory.herokuapp.com that makes it really easy to get up and running on Heroku.
    - IgorPartola 15y ago
      Cool. That's good to know. FWIW, this is the kind of project I would contribute to, was my plant not so full currently.