-
Notifications
You must be signed in to change notification settings - Fork 1
Setting up Gulp Deploy for Windows
This all has to happen in git bash. If your vagrant box has already been set up with these steps, you can just use steps 3, 6 and 7.
List the keys that have been added to ssh-agent, if your key is not list it, then add it. List again to double check.
ssh-add -L
eval `ssh-agent -s`
ssh-add ~/.ssh/id_rsa
ssh-add -L
The location of your key file may be different than the default location, so adjust accordingly.
SSH into vagrant and test your connection to Github. If you are successful, then your ssh-agent-forwarding works!
vagrant ssh
ssh -v -T git@github.com
Make sure the key you added in step 1 is also added to your Github account.
Go to the plugin or theme path and npm install.
cd /to/path/of/plugin/or/theme
npm install --no-bin-links
The --no-bin-links argument will prevent npm from creating symlinks for any binaries the package might contain.
npm install -g gulp
sudo ln -s node_modules/gulp/bin/gulp.js /usr/bin/gulp
A symbolic link (also symlink or soft link) is the nickname for any file that contains a reference to another file or directory in the form of an absolute or relative path and that affects pathname resolution.
You need the server hostname and the destination is the path on the server for deployment
You may have to add the RSA fingerprint to your known hosts file, just say yes.
gulp deploy
You should see a list of the files that are being synced between your VM and the server.