Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[doc fix] Mention proper communication mechanism used by carapace
We ceased to use `hook.io` for `haibu-carapace` long time ago but forgot
to update `README.md`.

Fixes nodejitsu/haibu#131.
  • Loading branch information
mmalecki committed Dec 28, 2012
1 parent 26396d6 commit bd76519
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -12,7 +12,7 @@ haibu is the open-source [node.js](http://nodejs.org) project used at [Nodejitsu

haibu (which is Japanese for "hive") recieves commands for spawning, transforming, and managing multiple node.js applications. Haibu utilizes a unique approach by wrapping spawned Node.js applications in a "[Carapace](https://github.com/nodejitsu/haibu-carapace)" which allows haibu to extend spawned applications with all sorts of additional functionaltiy. When haibu wraps a node.js application in a "carapace" the application becomes a "drone".

This approach allows haibu to directly interact with node.js applications and add all sorts of additional functionality. [Carapace](https://github.com/nodejitsu/haibu-carapace) also contains a plugin system including functionality for things like: chroot, chdir, and even a [http://hook.io](hook.io) bridge.
This approach allows haibu to directly interact with node.js applications and add all sorts of additional functionality. [Carapace](https://github.com/nodejitsu/haibu-carapace) also contains a plugin system including functionality for things like: chroot, chdir, and `node`'s built-in IPC.

## Where can I run haibu?

Expand Down

0 comments on commit bd76519

Please sign in to comment.