phantom-phoenix - npm Package Compare versions

Comparing version 1.4.4 to 1.4.5

package.json

		{
		"name": "phantom-phoenix",
		"description": "Redis based phantomjs queue and runner",
		"version": "1.4.4",
		"keywords": [
		"phantom",
		"phantomjs",
		"queue",
		"pubsub",
		"tasks",
		"jobs",
		"runner",
		"task-runner"
		],
		"homepage": "https://github.com/sdslabs/phoenix",
		"bugs": {
		"url" : "https://github.com/sdslabs/phoenix/issues"
		},
		"author": {
		"name" : "Abhay Rana",
		"email" : "nemo@sdslabs.co.in",
		"url" : "https://captnemo.in"
		},
		"preferGlobal": true,
		"repository": "sdslabs/phoenix",
		"license" : "MIT",
		"version": "1.4.5",
		"dependencies": {
		@@ -6,0 +28,0 @@ "clone": "^1.0.2",

README.md

		@@ -1,6 +0,6 @@
		#Phoenix [![Build Status](https://travis-ci.org/sdslabs/phoenix.svg?branch=master)](https://travis-ci.org/sdslabs/phoenix)
		# Phoenix [![Build Status](https://travis-ci.org/sdslabs/phoenix.svg?branch=master)](https://travis-ci.org/sdslabs/phoenix)

		Redis based phantomjs queue

		##Instructions
		## Instructions

		@@ -11,3 +11,3 @@ * Install `redis` (https://github.com/antirez/redis)

		##Usage
		## Usage

		@@ -28,7 +28,7 @@ By default it subscribes to a single channel specified in the config

		##Injection
		## Injection
		By setting the `js` key in config.yml you can run code on the loaded web page before the page is
		loaded itself.

		##Logging
		## Logging
		phoenix logs every phantomjs instance. For every instance that is created, a new temporary
		@@ -44,3 +44,3 @@ directory is created in the logs directory. The config passed to phantomjs is stored in the `config.json`

		##Usage
		## Usage
		Instead of cloning and running the entire repo for each project, you can use the npm package
		@@ -63,3 +63,3 @@ (called `phantom-phoenix`), which has its own binary called `phoenix` which you can run.

		##Redis
		## Redis

		@@ -66,0 +66,0 @@ Instead of just using a redis pubsub, we use a hybrid pubsub+list model as queue to store logs. Instead

Fixed alerts