Installations
npm install grunt-rsync-2
Developer Guide
Typescript
No
Module System
CommonJS
Min. Node Version
>= 0.8.0
NPM Version
1.2.32
Score
57.2
Supply Chain
91.7
Quality
72.4
Maintenance
25
Vulnerability
98.2
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (87.69%)
Erlang (12.31%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
maxdaten
Download Statistics
Total Downloads
21,453
Last Day
1
Last Week
15
Last Month
28
Last Year
118
GitHub Statistics
12 Stars
34 Commits
8 Forks
4 Watching
2 Branches
3 Contributors
Package Meta Information
Latest Version
0.1.3
Package Id
grunt-rsync-2@0.1.3
Size
4.84 kB
NPM Version
1.2.32
Total Downloads
Cumulative downloads
Total Downloads
21,453
Last day
0%
1
Compared to previous day
Last week
400%
15
Compared to previous week
Last month
1,300%
28
Compared to previous month
Last year
-22.4%
118
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
grunt-rsync-2
Copy files to a (remote) machine running an SSH daemon with 'rsync'.
See also: https://github.com/jedrichards/grunt-rsync
Getting Started
rsync
has to be installed on the local and remote system. rsync
must be able to connect to the host without password (e.g. public key authentication)
Install with: npm install grunt-rsync-2
Inside your grunt.js
file add :
1grunt.loadNpmTasks('grunt-rsync-2');
and a task named rsync
(see Configuration)!
Configuration
Add a configuration like this:
1grunt.initConfig({ 2 ... 3 rsync: { 4 deploy: { 5 files: 'dist/', 6 options: { 7 host : "example.com", 8 port : "1023", 9 user : "jdoe", 10 remoteBase: "~/production" 11 } 12 } 13 }, 14 ... 15});
This will transfer the content of the dist
directory (relative to the current directory) to the host directory ~/production
(relative to the user home) on the host example.com:1023
logged in with jdoe
.
Warning: Files on the remote machine will be overridden
File option: files
files
: defines the files and directories to transfer from local to remote machine.files
can be an String (supports grunts globbing) or a map of<String>:<String>
or<String>:[<String>]
.
Examples:
Simple file-descriptor:
1rsync: { 2 deploy: { 3 files: 'dist/**/*.jpg' // globbing 4 ... 5 } 6}
selects all jpg-images from all directories in dist
Mapping single file-descriptor:
1rsync: { 2 deploy: { 3 files: {'images/' : 'dist/**/*.jpg'} // map <String>:<String> 4 options: { 5 ... 6 remoteBase: "~/production" 7 } 8 } 9}
selects all jpg-images from all directories in dist
to remote ~/production/images/
Mapping multiple file-descriptor:
1rsync: { 2 deploy: { 3 files: {'images/' : ['dist/images/*.jpg', 'dist/img/*.jpg']} // map <String>:[<String>] 4 options: { 5 ... 6 remoteBase: "~/production" 7 } 8 } 9}
selects all jpg-images from images
and img
directories in dist
to remote ~/production/images/
rsync options: options
host
: the hostname or ip (ip4/ip6). Default:localhost
port
: the port of the ssh server on the host. Default:22
user
: the user name on the remote to log in with.remoteBase
: the path from root (defined by the ssh server) to the directory to place the content in. Default:~
preserveTimes
: keeps the origin timestamp. Default:false
preservePermissions
: keeps the rights. Default:true
compression
: transfer with compression. Default:true
recursive
: transfer the source directory recursivly Default:true
additionalOptions
: rsync commandline arguments (seeman rsync
) Default:''
Release History
0.1.1 - initial release to github and npm
License
Copyright (c) 2012 Jan-Philip Loos Licensed under the MIT license.
TODO
![Empty State](/_next/static/media/empty.e5fae2e5.png)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE-MIT:0
- Info: FSF or OSI recognized license: MIT License: LICENSE-MIT:0
Reason
Found 2/25 approved changesets -- score normalized to 0
Reason
project is archived
Details
- Warn: Repository is archived.
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 7 are checked with a SAST tool
Score
3
/10
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More