{"_id":"grunt-ftpush","_rev":"32-ab624c0dac25a734e9ec182728bd1b8f","name":"grunt-ftpush","description":"Incrementally deploy data over the FTP protocol","dist-tags":{"latest":"0.3.3"},"versions":{"0.1.0":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.0","homepage":"https://github.com/inossidabule/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabule/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabule/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Dependencies\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.0","dist":{"shasum":"8fd44c89268fa15770d1564bfe60bbdf08ddb93f","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.0.tgz","integrity":"sha512-xV0Nix2nfwCSQWFd8rMNggkr0TfjF8c9iFrWxhFDOGlQy90I3Zu7Dl3zgkfvsghG/H6gTCW0JeoeKBWo+Pc6rw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDQDkL14bO9HU+z4Wc6l7QVmCoOcWi86d9tv/7ahWOJqgIhAIF8uhRPOdvYv285Vb3gCI2o+vsnd6u+SNJ5OhJHfZAn"}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.1":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.1","homepage":"https://github.com/inossidabule/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabule/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabule/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Dependencies\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.1","dist":{"shasum":"9cfb4ff6a6df614aaaba799bc524a98ac954bdc5","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.1.tgz","integrity":"sha512-Smkm5+7ZWP4aLV7P92vQ8i217smsEM0keNYIYZUZB3qZL0pJY3qMN1tYkmk4hll6ZfbTVX6c0URiKizLpX0jNw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFOOKa00/t/KhHIiSWU2Dgcx98zUI1zJSn9LgxiAFS4gIhAPW2exqEStG0NlE/rYJPJuyUmFUTW0a3nh8WwigH2oTA"}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.2":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.2","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.2","dist":{"shasum":"5a8cbd521833a8d310569ab9fb8742b59153ef49","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.2.tgz","integrity":"sha512-Qo0WPGIdn9aVanMVZTZkHyb/YqRMLEtkf+IQ5n3fEvqGxkMQwcjNQui6sPjf7PNobCdh0XESHMplB0Sj7ctacA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDyJ+TeP8VCh06ZZtLYRqcAVu3dWLa4eJvipLB6f9qxzgIhAI1gYa5BO9MWYdl3KJoUoN92hRMBQxidBWSwLuKUnu0t"}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.3":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.3","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.3","dist":{"shasum":"68f1cf82fac2a48d7f9dc71b6704270f52949da6","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.3.tgz","integrity":"sha512-4vv8mAO5egkh5trCNdeb1JcmeRrgUEwhaPO9z4vYKFRsiw8083cSxzSOV8ViRYnNvUYnigMElTrWNq4zzteGPQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA0mOb/TwY7ZyYpeBlkXCzeWfrMDRReaoAmpjTN9mzutAiAmGmmgdGXUeDr1LLpWy5WcEANfG3hDah5viSul+uMzUA=="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.4":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.4","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.4","dist":{"shasum":"f8b411baf803c5009dab101fbef8ba4bd62d8d42","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.4.tgz","integrity":"sha512-aDNSA+bp63g3QldGwy3e1k9cqNIeJlnn5VALXXr+/OEanq8KyPT+T1wv6ArpEF6Ds/ur3gkWV2cpVD8T6Jg2Xw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDTdBAqcFHvHUis5KV38SRSdtEOxf66Zic4Y7N/NkGZkAIgIl95FqF1gGxzJ90MJuGYnfEdo4dUoaYmAGZA/gWIuCY="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.5":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.5","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.5","dist":{"shasum":"8a61f4aaa12bf2711353d99de5b7782048df9c73","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.5.tgz","integrity":"sha512-QVkxVjf9RxPvSpE4tj1zajUGj/O0bDi9pCEWaz17LY8Rh1NFKzxLWy9ZZjg13k09muCwwm26jy+oZt8xUJMo1g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCLTc/F8GxOb4ESNYE0s6wGD2OaBupne8pBM9mZ937PSwIgNWJdAUxxH039SJxe3eO8mw18QpifzLuzlDPkJcF+iVs="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.1.6":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.1.6","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.1.6","dist":{"shasum":"b05b79627842ffee264f62771d4108b5f4e31c28","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.1.6.tgz","integrity":"sha512-wkzXK+vonh9Zg6zF1mUdvzPVFgFVysFhHb1oaq5Yl0ql2IpqbNPoeeHOlI+imGe4p8uadJ1A6F5+inKdJ1V9zA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICfihOAScfLQ8g0ZRi23VXT8OpMiiF7wyjRy/JYhQ5IsAiAfndq8uKz9sxnlDgDuM9XZprnZsazWiKeJYUjtrFWyiw=="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.2.0":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.2.0","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.2.0","dist":{"shasum":"5087af73e9b10d6beb53fe00c25d43f872a35a2a","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.2.0.tgz","integrity":"sha512-DsGfaxXbbMLFQoU2dDN4JNHGd30iSSHYZ52wLafoks3mg2pTOLLkoEyIJxLSMn8KpavCjjdKWw+GENvxXZuukA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDjqXX8q3XsQ2GNgbxWJIwD1R8yc4+pn70+n0st2jwyvQIgFBhI6rtv3k0JzBvuE6Be8ro4avKVypNIdoY9Psk+dEk="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.2.1":{"name":"grunt-ftpush","description":"Incremenetal deployment over FTP","version":"0.2.1","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n[![endorse](http://api.coderwall.com/inossidabile/endorsecount.png)](http://coderwall.com/inossidabile)\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.2.1","dist":{"shasum":"008dccb0ccc242784edfc198fe0cd737336616bd","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.2.1.tgz","integrity":"sha512-IG0EfXrxEVkKTGsdDPELegbvbIHSaWxzJ1zGqgnWqsQBPvACHmK8wd0nPEc4c9OeYCUTjSz5Z/ze0OBu9FXpsA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDsP6IFa7D3ZQRzgA7Ogazrna63UAroyWX3FeMvhH9juAiAV5c/m36UoUL0g9J3vQMS6w4+5GCzVBDd03eL2KmbOLw=="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.2.2":{"name":"grunt-ftpush","description":"Package has been renamed to 'grunt-contrib-ftpush'!","version":"0.2.2","homepage":"https://github.com/inossidabile/grunt-contrib-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-contrib-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-contrib-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-contrib-ftpush\n\n[![NPM version](https://badge.fury.io/js/grunt-contrib-ftpush.png)](http://badge.fury.io/js/grunt-contrib-ftpush)\n\n> Incrementally deploy data over the FTP protocol.\n>\n> Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally\n> unlike its predecessor. It mirrors remote location to the given local location removing excess directories\n> and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## Getting Started\nThis plugin requires Grunt `~0.4.0`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install grunt-contrib-testem --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-contrib-testem');\n```\n\n## How to use\n\nWithin your Grunt configuration you have to define one or more bundles to upload:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nThe possible parameters of the configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.","readmeFilename":"README.md","_id":"grunt-ftpush@0.2.2","dist":{"shasum":"f383677c69d1c53caf9464b61d85337afb27b63b","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.2.2.tgz","integrity":"sha512-fZDhxNkIjZvuRgljO/J8PkUHglh1132qw+P90IrhWlJkMSayDdQQII+NXAWC6ZOCTC/CIN2699aN4ANCupm64g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBTcU5oWLorP5IsifDzQIugznq2EmC4Famd15HuXtWmEAiEAyrHboBP/ygqc+43vsmQI0SC5EDRPeywf5WK2BpG39tg="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"directories":{},"deprecated":"Please use grunt-contrib-ftpush"},"0.3.2":{"name":"grunt-ftpush","description":"Incrementally deploy data over the FTP protocol","version":"0.3.2","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.3.5"},"readme":"# grunt-ftpush\n\n[![NPM version](https://badge.fury.io/js/grunt-ftpush.png)](http://badge.fury.io/js/grunt-ftpush)\n\n> Incrementally deploy data over the FTP protocol.\n>\n> Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally\n> unlike its predecessor. It mirrors remote location to the given local location removing excess directories\n> and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## ATTENTION\n\nThis plugin is based on `jsftp` which may sometimes be pretty unstable. I will try hard to help you but its behavior may differ depending on the FTP server you connect to and I can't test them all.\n\n**Please consider the constant usage of `--simple` mode before raising an issue.**\n\nIn this mode ftpush won't delete any excessive files on the server. It won't even try to list what's on the server. Instead it will just make incremental upload of files that actually changed (which is probably the main thing you want).\n\nIf it works for you – add `simple: true` to your config and that's it!\n\n## Getting Started\nThis plugin requires Grunt `~0.4.0`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install grunt-ftpush --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\n## How to use\n\nWithin your Grunt configuration you have to define one or more bundles to upload:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp'],\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nThe possible parameters of the configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n- **simple** - if set to `true`, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.\n","readmeFilename":"README.md","_id":"grunt-ftpush@0.3.2","dist":{"shasum":"65d72fdda236cf728e37c341036ee6f796b4cb2f","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.3.2.tgz","integrity":"sha512-igsZp5TAR51DeOUHVvuKNQmJ35sYqwuetA39OTDRyMm3pUtN4dBfnyM+PJRrwf2EC3rhF06IGbh5XpSDrvSyfQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIH2yhHdrCjUbTL0SLG1rhWOgmTdXw7Sx3YZ8mMOq/Au+AiAgdmng0oe/mLVuFKkKad2mxz1W4Xtv8R8TzP+ApT5OAw=="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}]},"0.3.3":{"name":"grunt-ftpush","description":"Incrementally deploy data over the FTP protocol","version":"0.3.3","homepage":"https://github.com/inossidabile/grunt-ftpush","author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"bugs":{"url":"https://github.com/inossidabile/grunt-ftpush/issues"},"engines":{"node":"*"},"dependencies":{"jsftp":"~0.6.0","sugar":"~1.3.8","async":"~0.2.9","grunt":"~0.4.0"},"keywords":["gruntplugin"],"license":"MIT","devDependencies":{"grunt":"~0.4.1","grunt-release":"~0.6.0"},"readme":"# grunt-ftpush\n\n[![NPM version](https://badge.fury.io/js/grunt-ftpush.png)](http://badge.fury.io/js/grunt-ftpush)\n\n> Incrementally deploy data over the FTP protocol.\n>\n> Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally\n> unlike its predecessor. It mirrors remote location to the given local location removing excess directories\n> and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## ATTENTION\n\nThis plugin is based on `jsftp` which may sometimes be pretty unstable. I will try hard to help you but its behavior may differ depending on the FTP server you connect to and I can't test them all.\n\n**Please consider the constant usage of `--simple` mode before raising an issue.**\n\nIn this mode ftpush won't delete any excessive files on the server. It won't even try to list what's on the server. Instead it will just make incremental upload of files that actually changed (which is probably the main thing you want).\n\nIf it works for you – add `simple: true` to your config and that's it!\n\n## Getting Started\nThis plugin requires Grunt `~0.4.0`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install grunt-ftpush --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\n## How to use\n\nWithin your Grunt configuration you have to define one or more bundles to upload:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp'],\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nThe possible parameters of the configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n- **simple** - if set to `true`, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Options\n\nThe only possible option is: `--simple`. If given, task will upload modified files and quit, it will NOT remove redundant files and directories at the server side.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Kudos\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.\n\n## Maintainers\n\n* Boris Staal, [@inossidabile](http://staal.io)\n\n## License\n\nIt is free software, and may be redistributed under the terms of MIT license.\n\n[![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/inossidabile/grunt-ftpush/trend.png)](https://bitdeli.com/free \"Bitdeli Badge\")","readmeFilename":"README.md","_id":"grunt-ftpush@0.3.3","dist":{"shasum":"f4ea5905ee041b7d6b7b0e95d7e15ffd0cdac912","tarball":"https://registry.npmjs.org/grunt-ftpush/-/grunt-ftpush-0.3.3.tgz","integrity":"sha512-aLIEIm/g9dYxQmaRt6q9qrVbI26e3lVPP8OpdNqxPXp5Z8IOzM3LdG8S4u4FZlieF+XmojBwr4rI2OCSKc8EMg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEQhkrYKga+eEdr1kPZObkyWuoTcJEJLvaiaC2KPWX7BAiBCrDe0yLU8KnFN6PRRUEVj77YHT+6bcgZZ8Fz88379HA=="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"inossidabile","email":"boris@staal.io"},"maintainers":[{"name":"inossidabile","email":"boris@staal.io"}]}},"readme":"# grunt-ftpush\n\nThis is a [grunt](https://github.com/gruntjs/grunt) task for code deployment over the _ftp_ protocol. Being rewrite of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) it works incrementally unlike its predecessor. It mirrors remote location to the given local location removing excess directories and files. Additionally it tries to intellectually upload only changed files.\n\n**NOTE**: with the limited abilities of FTP, the only adequate way to track changes is to track them locally. It means that each run will compare set of files **to the previous run** and not the server state. Therefore:\n\n  * The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to `.grunt/ftpush`.\n  * If there are two users that deploy (or you use multiple machines), it will increment _all_ local changes. It can be considered safe but you might end up uploading a bit more.\n  * To make it reupload from the scratch, delete files located at `.grunt/ftpush/*`.\n\n## Usage\n\nTo use this task you will need to include the following configuration in your _grunt_ file:\n\n```javascript\nftpush: {\n  build: {\n    auth: {\n      host: 'server.com',\n      port: 21,\n      authKey: 'key1'\n    },\n    src: 'path/to/source/folder',\n    dest: '/path/to/destination/folder',\n    exclusions: ['path/to/source/folder/**/.DS_Store', 'path/to/source/folder/**/Thumbs.db', 'dist/tmp']\n    keep: ['/important/images/at/server/*.jpg']\n  }\n}\n```\n\nand load the task:\n\n```javascript\ngrunt.loadNpmTasks('grunt-ftpush');\n```\n\nThe parameters in our configuration are:\n\n- **host** - the name or the IP address of the server we are deploying to\n- **port** - the port that the _ftp_ service is running on\n- **authKey** - a key for looking up the saved credentials. If no value is defined, the `host` parameter will be used\n- **src** - the source location, the local folder that we are transferring to the server\n- **dest** - the destination location, the folder on the server we are deploying to\n- **exclusions** - an optional parameter allowing us to exclude files and folders by utilizing grunt's support for `minimatch`. Please note that the definitions should be relative to the project root\n- **keep** - an array of paths that should be kept on the server even when they are not presented locally. The definitions should be relative to `dest`.\n\n## Authentication parameters\n\nUsernames and passwords are stored as a JSON object in a file named `.ftppass`. This file should be located in the same folder as your `Gruntfile`. `.ftppass` should have the following format:\n\n```javascript\n{\n  \"key1\": {\n    \"username\": \"username1\",\n    \"password\": \"password1\"\n  },\n  \"key2\": {\n    \"username\": \"username2\",\n    \"password\": \"password2\"\n  }\n}\n```\n\nThis way we can save as many username / password combinations as we want and look them up by the `authKey` value defined in the _grunt_ config file where the rest of the target parameters are defined.\n\n**IMPORTANT**: make sure that the `.ftppass` file uses double quotes (which is the proper _JSON_ syntax) instead of single quotes for the names of the keys and the string values.\n\n## Dependencies\n\nThis task is a fork of [grunt-ftp-deploy](https://github.com/zonak/grunt-ftp-deploy) by [zonak](https://github.com/zonak).\n\nIt also is built by taking advantage of the great work of Sergi Mansilla and his [jsftp](https://github.com/sergi/jsftp) _node.js_ module and suited for the **0.4.x** branch of _grunt_.","maintainers":[{"name":"inossidabile","email":"boris@staal.io"}],"time":{"modified":"2022-06-18T15:02:54.674Z","created":"2013-07-10T17:02:23.991Z","0.1.0":"2013-07-10T17:02:31.677Z","0.1.1":"2013-07-10T19:22:18.857Z","0.1.2":"2013-07-18T14:27:57.933Z","0.1.3":"2013-07-29T12:00:59.339Z","0.1.4":"2013-07-29T15:11:55.428Z","0.1.5":"2013-07-29T15:54:47.955Z","0.1.6":"2013-07-30T20:36:03.064Z","0.2.0":"2013-08-01T12:33:44.172Z","0.2.1":"2013-08-16T09:05:05.944Z","0.2.2":"2013-08-20T09:15:13.769Z","0.3.2":"2013-10-04T14:50:01.594Z","0.3.3":"2013-11-11T12:23:09.322Z"},"author":{"name":"Boris Staal","email":"boris@staal.io"},"repository":{"type":"git","url":"git://github.com/inossidabile/grunt-ftpush.git"},"users":{"hansspiess":true,"reno184":true,"afelicioni":true,"jmm23":true}}