Library building and executing rsync
commands with Node.js.
This project is forked from the excellent rsync module, because I wanted to play with some ideas.
Node.js v6 or newer.
Installation goes through NPM:
$ npm install rsync
const rsync = require('rsync');
// Build the command
const cmd = rsync().shell('ssh')
.setFlags('az')
.source('/path/to/source')
.destination('server:/path/to/destination');
// Execute the command
cmd.execute()
.then(() => {
console.log('All done executing', cmd);
})
.catch(err => {
console.error(err);
});
For more examples see the examples
directory.
Construct a new Rsync command instance. The constructor takes a single options
object, with the following properties:
executable
: path torsync
executable (default:rsync
found inPATH
)stdout
: custom stream forstdout
output (default:process.stdout
)stderr
: custom stream forstderr
output (default:process.stderr
)stdin
: custom stream forstdin
input (default:process.stdin
)
const {Rsync} = require('rsync');
const cmd = new Rsync({
executable: '/usr/local/bin/rsync',
stdout: process.stdout,
stderr: process.stderr,
stdin: process.stdin
});
Set an option. This can be any option from the rsync manual. The value is optional and only applies to options that take a value. This is not checked however. Supplying a value for an option that does not take a value will append the value regardless. This may cause errors when the command is executed.
cmd.set('a')
.set('progress')
.set('list-only')
.set('exclude-from', '/path/to/exclude-file');
Options must be unique and setting the same option twice will override any existing value. For options that can be set multiple times special methods exist (see accessor methods). Any leading dashes (-) are stripped when setting the option.
The set
method is chainable.
Unset an option. Any leading dashes (-) are stripped when unsetting an option.
cmd.unset('progress')
.unset('quiet');
The unset
method is chainable.
Set one or more flags. Flags are single letter options without a value, for example compress (-z
) or archive (-a
).
The following are equivalent:
cmd.setFlags('avz');
cmd.setFlags('a', 'v', 'z');
cmd.setFlags(['a', 'v', 'z']);
cmd.setFlags(['avz']);
cmd.setFlags(['a', 'v'], ['z']);
The setFlags
method is chainable.
Unset one or more flags. Flags are single letter options without a value, for example compress (-z
) or archive (-a
).
The following are equivalent:
cmd.unsetFlags('avz');
cmd.unsetFlags('a', 'v', 'z');
cmd.unsetFlags(['a', 'v', 'z']);
cmd.unsetFlags(['avz']);
cmd.unsetFlags(['a', 'v'], ['z']);
The setFlags
method is chainable.
Check if an option is set.
This method does not check alternate versions for an option. When an option is set as the short version this method will still return false
when checking for the long version, event though they are the same option.
cmd.set('quiet');
cmd.isSet('quiet'); // is TRUE
cmd.isSet('q'); // is FALSE
Get the value for an option by name. If a valueless option is requested null will be returned.
cmd.option('rsh'); // returns String value
cmd.option('progress'); // returns NULL
Get the arguments list for the command that is going to be executed. Returns an Array with the complete options that will be passed to the command.
Get the complete command that is going to be executed.
const cmd = rsync()
.shell('ssh')
.flags('az')
.source('/p/t/source')
.destination('server:/p/t/dest');
const c = cmd.command();
// c is "rsync -az --rsh="ssh" /p/t/source server:/p/t/dest
Set or get the value for rsync process cwd.
cmd.cwd(__dirname); // Set cwd to __dirname
cmd.cwd(); // Get cwd value
Set or get the value for rsync process environment variables.
Default: process.env
cmd.env(process.env); // Set env to process.env
cmd.env(); // Get env values
Register output handler functions for the commands stdout and stderr output. The handlers will be called with streaming data from the commands output when it is executed.
cmd.output(
function(data){
// do things like parse progress
}, function(data) {
// do things like parse error output
}
);
This method can be called with an array containing one or two functions. These functions will
be treated as the stdoutHandler and stderrHandler arguments. This makes it possible to register
handlers through the Rsync.build
method by specifying the functions as an array.
const cmd = Rsync.build({
// ...
output: [stdoutFunc, stderrFunc] // these are references to functions defined elsewhere
// ...
});
Execute the command. options
accepts two props, stdoutHandler
and stderrHandler
.
When stdoutHandler
and stderrHandler
functions are provided they will be used to stream
data from stdout and stderr directly without buffering. Any output handlers that were
defined previously will be overwritten.
If called with a Node-style callback function, this function returns the ChildProcess
object, which can be used to kill the rsync process or clean up if the main program exits early.
// signal handler function
const quitting = function() {
if (child) {
child.kill();
}
process.exit();
}
process.on("SIGINT", quitting); // run signal handler on CTRL-C
process.on("SIGTERM", quitting); // run signal handler on SIGTERM
process.on("exit", quitting); // run signal handler when main process exits
// simple execute
const child = cmd.execute(function(error, code, cmd) {
// we're done
});
// execute with stream callbacks
const child = cmd.execute(
function(error, code, cmd) {
// we're done
}, function(data){
// do things like parse progress
}, function(data) {
// do things like parse error output
}
);
// no ChildProcess
cmd.execute().then(() => {
// we're done
})
The following option shorthand methods are available:
- shell(value):
--rsh=SHELL
- delete():
--delete
- progress():
--progress
- archive():
-a
- compress():
-z
- recursive():
-r
- update():
-u
- quiet():
-q
- dirs():
-d
- links():
-l
- dry():
-n
- chmod(value):
--chmod=VALUE
(accumulative) - hardLinks():
-H
- perms():
-p
- executability():
-E
- owner():
-o
- group():
-g
- acls():
-A
- xattrs():
-X
- devices():
--devices
- specials:
--specials
- times():
-t
All shorthand methods are chainable as long as options that require a value are provided with one.
These methods can be used to get or set values in a chainable way. When the methods are called without arguments the current value is returned. When the methods are called with a value this will override the current value and the Rsync instance is returned to provide the chainability.
Get or set the executable to use as the rsync command.
Get or set the destination for the rsync command.
Get or set the source or sources for the rsync command. When this method is called multiple times with a value it is appended to the list of sources. It is also possible to present the list of source as an array where each value will be appended to the list of sources
// chained
cmd.source('/a/path')
.source('/b/path');
// as Array
cmd.source(['/a/path', '/b/path']);
In both cases the list of sources will contain two paths.
Register a list of file patterns to include/exclude in the transfer. Patterns can be registered as an array of Strings or Objects.
When registering a pattern as a String it be prefixed with a +
or -
sign to
signal include or exclude for the pattern. The sign will be stripped of and the
pattern will be added to the ordered pattern list.
When registering the pattern as an Object it must contain the action
and
pattern
keys where action
contains the +
or -
sign and the pattern
key contains the file pattern, without the +
or -
sign.
The order of patterns is important for some rsync commands. The patterns are stored in the order
they are added either through the patterns
method or the include
and exclude
methods. The
patterns
method can be used with Rsync.build
to provide an ordered list for the command.
// on an existing Rsync object
cmd.patterns([ '-.git', { action: '+', pattern: '/some_dir' });
// through Rsync.build
const command = Rsync.build({
// ...
patterns: [ '-.git', { action: '+', pattern: '/some_dir' } ]
// ...
});
Exclude a pattern from transfer. When this method is called multiple times with a value it is appended to the list of patterns. It is also possible to present the list of excluded patterns as an array where each pattern will be appended to the list.
// chained
cmd.exclude('.git')
.exclude('.DS_Store');
// as Array
cmd.exclude(['.git', '.DS_Store']);
Include a pattern for transfer. When this method is called multiple times with a value it is appended to the list of patterns. It is also possible to present the list of included patterns as an array where each pattern will be appended to the list.
// chained
cmd.include('/a/file')
.include('/b/file');
// as Array
cmd.include(['/a/file', '/b/file']);
For convenience there is the build
function on the Rsync contructor. This function can be
used to create a new Rsync command instance from an options object.
For each key in the options object the corresponding method on the Rsync instance will be called. When a function for the key does not exist it is ignored. An existing Rsync instance can optionally be provided.
const {Rsync} = require('rsync');
const cmd = Rsync.build({
source: '/path/to/source',
destination: 'server:/path/to/destination',
exclude: ['.git'],
setFlags: 'avz',
shell: 'ssh'
});
cmd.execute(function(error, stdout, stderr) {
// we're done
});
Differences between this and rsync
execute()
returns aPromise
when not called with a callbackflags()
is deprecated in lieu ofsetFlags()
andunsetFlags()
- Support for custom
STDOUT
,STDERR
andSTDIN
streams - Default export is
rsync()
function which wraps the constructor of theRsync
class; theRsync
class is now a property thereof:const {Rsync} = require('rsync'); const rsync = require('rsync'); const a = rsync().setFlags('avz'); const b = new Rsync().setFlags('avz');
If there is something missing (which there probably is) just fork, patch and send a pull request.
For adding a new shorthand method there are a few simple steps to take:
- Fork
- Add the option through the
exposeShortOption
,exposeLongOption
orexposeMultiOption
functions. For examples see the source file. - Update this README file to list the new shorthand method
- Make a pull request
When adding a shorthand make sure it does not already exist, it is a sane name and a shorthand is necessary.
If there is something broken (which there probably is), the same applies: fork, patch, pull request. Opening an issue is also possible.
v1.0.0
- Forked to
@boneskull/rsync
v0.6.1
- Add support for windows file paths under cygwin (#53)
v0.6.0
- Escape dollar signs in filenames (#40)
- Add permission shorthands (#46)
- Added env() option to set the process environment variables (#51)
v0.5.0
- Properly treat flags as String
- Differentiate between shell and file arguments (escaping)
- Added a bunch of unit tests
- Added TravisCI setup to run tests on branches and PRs
- Added cwd() option to set the process CWD (#36)
v0.4.0
- Child process pid is returned from
execute
(#27) - Command execution shell is configurable for Unix systems (#27)
- Better escaping for filenames with spaces (#24)
v0.3.0
- Launch the command under a shell (#15)
- Typo fix isaArray -> isArray for issue (#14)
- Error: rsync exited with code 14 (#11)
v0.2.0
- use spawn instead of exec (#6)
v0.1.0
- better support for include/exclude filters
- better support for output handlers
- removed output buffering (#6)
v0.0.2
- swapped exclude and include order
- better shell escaping
v0.0.1
- initial version (actually the second)
This module is licensed under the MIT License. See the LICENSE
file for more details.