Marak
Marak
https://github.com/digitalocean has stepped up and sponsored hook.io for a year of hosting. We should add their logo to the homepage and add them to a small page of all our...
@janaka This looks awesome! I've opened a PR to begin to review the changes for .net support. I've been planning on doing a new release soon, so let me know...
Currently PHP services use `$Hook['params']` scope for merged get and post variables. It would be somewhat less surprising for PHP users if we also populated PHP's `$_GET` and `$_POST` scopes...
We should have an integration test that iterates through all supported programming languages and attempts to assert the responses of all hello world / echo services located in https://github.com/Stackvana/microservice-examples, per...
It seems it's possible to execute arbitrary bash commands through HTTP parameters when using bash services ( and other possible languages too ). This isn't intended behavior and should be...
Currently, the signature for Node.js functions is: `function (hook)`. It would be more clear to users and node.js friendly if the signature was: `function(req, res)`. The new function signature would...
Right now we are sending all HTTP params for `golang` and `rust` as individual `argv` arguments. It would be better if we sent the HTTP params as JSON and updated...
Now that we have a good way to compile source code into binaries, we should update the `coffee-script` and `babel` code paths to use the new compiled language plugin /...
Currently, all Node.js services are spawned in a new process using the `micro-node` binary, which is called via `microcule.spawn`. This ensures process level isolation of the untrusted source code. Inside...
The core spawning logic at https://github.com/Stackvana/microcule/blob/master/lib/plugins/spawn/index.js currently has two concerns coupled together: preparing the service options for spawning, and managing the spawned service. `microcule`'s spawning logic should only be concerned...