		@@ -27,3 +27,8 @@ # cluster-service

		Stability:

		With the ```v0.5``` release we're effectively at an "Alpha" stage, with some semblance
		of interface stability. Any breaking changes from now on should be handled gracefully
		with either a deprecation schedule, or documented as a breaking change if necessary.


		@@ -46,3 +51,2 @@ ## Getting Started

		```
		"scripts": {
		@@ -54,4 +58,5 @@ "start": "cservice server.js --accessKey lksjdf982734"
		}
		```

		Now we can leverage ```npm``` to find our local install of ```cluster-service```:

		npm start
		@@ -89,7 +94,7 @@

		You can even pipe raw JSON, which can be parsed and processed by the caller:
		You can even pipe raw JSON, which can be processed by the caller:

		cservice "restart all" --accessKey "my_access_key" --json

		Check out Cluster Commands for more details.
		Check out *Cluster Commands* for more details.

		@@ -218,3 +223,3 @@

		Indicate the worker is NOT ready, via ```workers``` option:
		Indicate the worker is NOT ready, via ```ready``` option:

		@@ -242,3 +247,4 @@ require("cluster-service").start({ workers: { "async_worker.js": { ready: false } } });

		Commands may be granted "inproc" (no trust), "local" (low trust), or "remote" (default). Setting access control at compile time can be done within the command, like so:
		Commands may be granted "inproc" (no trust), "local" (low trust), or "remote" (default). Setting
		access control at compile time can be done within the command, like so:

		@@ -264,3 +270,3 @@ ```javascript
		Combining the Worker Process (Cluster) model with a CLI piped REST API enables the ability
		command the already-running service to replace existing workers with workers in a
		to command the already-running service to replace existing workers with workers in a
		different location. This capability is still a work in progress, but initial tests are promising.
		@@ -267,0 +273,0 @@

cluster-service - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics