depend on the propagit version without the infinite loop bug
pass through the remote value from the fleet.json
Change strategy for detecting current directory

Allows fleet to be run via sudo/su.

Useful when creating an upstart job without having to run fleet as root.
0.1.6
Add a tips section

Even though running Fleet is pretty straight forward, if you have multiple instances running on the same server you will need to be aware that it consumes multiple ports.
Clarified what each port is used for.
Merge pull request #47 from ccowan/master

Added a "tips" section
stderr should go to stderr via console.error