What work needs to be done with Ruby support?

[dydx]

Interested in knowing how I might be able to help with Ruby support with hook.io. Low hanging fruit, big problems, etc. Willing to contribute as best I can.

[Marak]

@dydx -

Glad you asked!

The biggest feature-set missing from the additional languages right now is the ability to communicate non-http streams to it's parent process spawning process over STDIO channels 3 and 4. Fixing this will enable features such as logging and cloud datastore ( see: https://github.com/bigcompany/hook.io/issues/144 )

That specific issue is not as complex as it might seem. I am currently working with @pyhedgehog on similar support for Python.

I would recommend using the Ruby service / implementation a bit and see what limitations you hit / what doesn't make sense / what isn't best practice. We also have no support for gems, so I'd assume we'll want to implement similar package support to what we have for automatic installs with npm now.

There are a few of us in #hook.io on irc.freenode.net. We are actively discussing project development in there on most days.

[Marak]

In regards to gems, Ruby package management, and package management for any language, I have created a new repo hook.io-packages https://github.com/bigcompany/hook.io-packages/

To add gem support for Ruby will require creating a new binary that can install ruby dependencies programmatically to a directory. Here is the example one for node / npm: https://github.com/bigcompany/hook.io-packages/blob/master/bin/install-package-npm

[dydx]

@Marak

Interesting; I'm still playing with things, seeing where I run into problems. The code for the ruby hook looks fairly simple, though comparing to the node hook I can see what you mean about wanting to add some better features.

[Marak]

Renamed hook.io-packages to hpm.

Gems code will go here: https://github.com/bigcompany/hpm/tree/master/lib/gems