Do not scale down workers if there are more than one working worker.

When after_perform_scale_down is called it will always have at least one working worker, which is itself, but it may have more workers working.

We can't just scale down based on the number of pending jobs, because if multiple jobs are queued at the same time and we have this many number of workers, we may have many working jobs and no pending job, yet we can't kill those workers.

By checking if there are any working workers besides the job itself we prevent this from happening.
Using ps_scale heroku command instead of set_workers to be compatible with Cedar apps
Merge pull request #3 from vicentemundim/master

Do not scale down workers if there are more than one working worker
Switch to bundle gem instead of jeweler, rspec instead of test unit and heroku-api instead of heroku
Completed doc and spec
Move thresholds into yaml config file
Add commands for memo
Add changelog
Add protection of envionment of execution
Update version
Add safe mode
Merge pull request #2 from joel/safe_mode

Add safe mode
scale_down_on_failure
Merge pull request #3 from joel/scale_down_on_failure

scale_down_on_failure
Changes name from heroku-resque-auto-scale to heroku-resque-workers-scaler
Changes Name
Changed README to .md
Corrected authorized check on thresolds instead of environments
fixing issue in development where queued jobs won't run due to nil <= check
Merge github.com:pbrumm/heroku-resque-workers-scaler

Conflicts:
	VERSION
	heroku-resque-auto-scale.gemspec
	lib/heroku-resque-auto-scale.rb