Now you can set your own config file (an object/JSON) on the constructor of DPLOY if you don't want to use the YAML file.

t task (#24), where you can set the options directly on your
Gruntfile.js.

It's fairly simple to use:

```
var DPLOY = require("dploy");
var settings = {
    host: 'ftp.example.com',
    user: 'user',
    pass: 'password',
    path: {
        remote: 'public_html/',
        local: ''
    }
}

new DPLOY(settings, function() {
    console.log("Upload completed");
});
```

Where the first parameter is the config file for that server and the
second one is a callback for when the upload is completed. Both are
optional, of course.
Release v1.0.9
Added publicKey and privateKey settings

As requested in #18, now if you are using SFTP, you can set the path of
your `privateKey` or `publicKey` in the config file - DPLOY will do the
rest.

There’s also one more sweet thing: if you don’t set a password,
publicKey or privateKey, DPLOY will prompt you to type the password
manually. That works for both FTP or SFTP.

Some other methods were refactored and the logs are now improved
(specially to handle errors), so we can debug what happens a bit more.

Resolves #18.
Added support for FTPS

Two new settings for config file were added to support FTPS connections.
Since the library [node-ftp](https://github.com/mscdex/node-ftp) had
support for it, I’ve just added support for those new options.

The `secure` tag is default to `false` and it accepts `true` for both
control and data connection encryption, `control` for control
connection encryption only, or `implicit` for implicitly encrypted
control connection.

The `secureOptions` should be used together with the `secure` mode.
Release v1.1.0
Merge branch 'master' of https://github.com/LeanMeanFightingMachine/dploy

Conflicts:
	package.json
	src/dploy.coffee