3 ms·
For one script (deploy), that's 148 characters I don't have to type. Repeatedly, as changes are made. Just `gulp deploy` and it's done. Beyond that, I'm more co
by chrisfinazzo 8y ago
For one script (deploy), that's 148 characters I don't have to type. Repeatedly, as changes are made. Just `gulp deploy` and it's done. Beyond that, I'm more comfortable in bash, so I'd like to not waste that effort by moving to something else.
- yakshaving_jgt 8y agoRight, but then why not use bash by itself? Why wrap it in JavaScript at all?
- chrisfinazzo 8y agoI'm not typing [this][1] often if I can help it. [1]: https://raw.githubusercontent.com/chrisfinazzo/blog/master/gulpfile.js https://raw.githubusercontent.com/chrisfinazzo/blog/master/g...
- yakshaving_jgt 8y agoRight, but why would you need to? You said you were more comfortable in bash, so why not just do it in bash? Or Make? #!/usr/bin/bash set -e git push origin master rsync -crz \ --exclude-from='rsync-exclude.txt' \ --delete _site/ \ cfinazzo1@chrisfinazzo.com:/home/cfinazzo1/chrisfinazzo.com Stick that in a file called `deploy`, run `chmod +x deploy`, and then you can invoke it with `./deploy`. Make would be something similar. In fact your entire Gulpfile in Make would look like this: .PHONY: doctor build serve deploy doctor: bundle exec jekyll doctor build: doctor time bundle exec jekyll build --incremental serve: doctor time bundle exec jekyll serve --incremental deploy: git push origin master rsync -crz \ --exclude-from='rsync-exclude.txt' \ --delete _site/ cfinazzo1@chrisfinazzo.com:/home/cfinazzo1/chrisfinazzo.com