Patrick Stadler

Check this: https://github.com/pstadler/flightplan/issues/82#issuecomment-110849208

I agree, this makes sense.

Also consider to pass the directory if this makes any sense (see #107)

Take this into account: #109

That's definitely the way to go. rsync is a nightmare to utilize in the way that flightplan does. I'm thinking about replacing it with sftp.

Pretty busy at the time, but I'm open for pull requests 👍

Definitely thinking about adding that.

I'm planning to change the API in upcoming versions. `local()` and `remote()` are probably gonna be replaced with something like `task(name[, deps], function(local, remote) {})`. This would solve your problem.

You can programmatically run Flightplan: ``` javascript // flightplan.js var plan = module.exports = require('flightplan'); // export instance ... // api.js var plan = require('./flightplan'); // load instance from local...

This is a limitation of how the transfer function utilizes rsync. The simplest solution I can think of would be to create or move `package.tar.gz` into the current **project root**...