-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy successfully, but in fact the file doesn't rsync to remote server and no error happens #6
Comments
I add an argument rsync --delete -v -az public/ -e ssh webapp@139.xxx.xxx.65:/opt/blog/ and it run successfully,the public folder is sent to the remote server. |
I also encountered the problem today. It seems a new bug. |
Or manually set the value of |
Thanks @BurningDog I can use it |
This repo has 2 issues and 2 PRs.. All because of the missing port. If you can't fix that issue right now, you could just update the docs, that there is no default port.. Otherwise this one line should also fix the bug: |
@leesei yep, I think so |
FWIW I just installed hexo-deployer-rsync 0.1.1. I had to specify
Also when it wasn't actually working before I specified the port, it gave no indication that it wasn't working. It looked like it was working for this first time user (me).
|
@jhalbrecht #11 is not pushed to npm. @tommy351 Care to update the npm version? |
Created a new hexo 'deleteme' Tested working.
|
Without specifying the port it did not work for me as well, no error, just no result. With it, like charm. |
I submitted a PR (#17) that resolves this. Will use the default SSH port when no port is specified, and whatever you specify otherwise.
Note: I also removed the port 22 default that was added recently, because that overrides the default port I defined in my |
Closed for sloved, thx @gboudreau |
My config in
_config.yml
is :And after i ran command:
hexo d
,the terminal show:But in fact ,the public folder wasn't sent to remote folder.
I try to fix the problem,and add console in
lib/deployer.js
:It shows :
The text was updated successfully, but these errors were encountered: