Adding ability to --force npm install.

This is required because we need a way to re-read the package.json file to pick up dependency changes.

Signed-off-by: Eric Richmond <ericr@indabamusic.com>
from force to npmforce

Signed-off-by: Eric Richmond <ericr@indabamusic.com>
Merge pull request #11 from indabamusic/add_force_to_deploy

Adding ability to --force npm install.
Added --npmforce option
process env should still override target.env in exec
Merge pull request #12 from indabamusic/exec_default_env

process env should still override target.env in exec
adds additional commands
logs to log
remove web commands
ssh should be interactive.
prevents pm2 commands from running after ssh has terminated
Run notification scripts after deploy.
Doesn't check success/failure of deploy, only prevents notification if ssh fails
0.1.3
0.2.0
Revert "0.2.0"

This reverts commit a4b80055c96b4ebd9615ae37173532166b1254c4.
deploying code is serious business
update dependencies; pend instead of batch
remove unused tests
Revert "process env should still override target.env in exec"

This reverts commit b967e40854cbd15099dee9864e456390480f0be6.

The local process environment of the person running rodent should not
override the target environment.

Also the `== null` was intentional.
readme: updated command usage
remove log command. we already have monitor

effectively reverts fb8379636c69264b

we also have exec which is a generic thing you can use instead of
updating rodent.