Incrementally deploy data over the FTP protocol
Incrementally deploy data over the FTP protocol.
Being rewrite of 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.
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:
- The first run will upload everything since we have no idea what's the state of a server. Current state will be saved to
- 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.
- To make it reupload from the scratch, delete files located at
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-contrib-ftpush --save-dev
Within your Grunt configuration you have to define one or more bundles to upload:
ftpush:build:auth:host: 'server.com'port: 21authKey: 'key1'src: 'path/to/source/folder'dest: '/path/to/destination/folder'exclusions: 'path/to/source/folder/**/.DS_Store' 'path/to/source/folder/**/Thumbs.db' 'dist/tmp'keep: '/important/images/at/server/*.jpg'
The possible parameters of the configuration are:
- host - the name or the IP address of the server we are deploying to
- port - the port that the ftp service is running on
- authKey - a key for looking up the saved credentials. If no value is defined, the
hostparameter will be used
- src - the source location, the local folder that we are transferring to the server
- dest - the destination location, the folder on the server we are deploying to
- 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
- 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
The 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.
Usernames and passwords are stored as a JSON object in a file named
.ftppass. This file should be located in the same folder as your
.ftppass should have the following format:
"key1":"username": "username1""password": "password1""key2":"username": "username2""password": "password2"
This 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.
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.
It also is built by taking advantage of the great work of Sergi Mansilla and his jsftp node.js module and suited for the 0.4.x branch of grunt.
- Boris Staal, @inossidabile
It is free software, and may be redistributed under the terms of MIT license.