Rsync authentication issue about shipit-deploy HOT 8 CLOSED

I am sorry but I don't know what can be the problem. You know Windows is not supported either as a deploy environment or either as a remote environment. Let me know if you find the problem.

from shipit-deploy.

@neoziro I didn't realize it was platform limited. I'd love to help out to bring about Windows as an environment from which you can deploy. It seems like the only issue currently is the improper key usage for rsync or something.

I looked through the code of Shipit for the remote copy and besides the pathing (using / instead of path.sep), it all looks good. I'll give fixing it a shot. This module honestly fulfills 90% of my business needs (beside the actual copying).

Also, question, is there a reason why the files get built locally and rsynced/etc. rather than checking out the repo remotely?

from shipit-deploy.

@AntJanus did you resolve your problem?

Yes the reason is that in most of case, the build phase is very expensive in term of CPU (uglify, etc..) so I prefer to do it on a CI server or on my machine to prevent lags on the remote server. It's not a good practice to run the build on a production server.

from shipit-deploy.

@neoziro I never really resolved the issue of using a custom ssh key and specifying the path to the key; however, adding the key to my ~/.ssh folder and adding the correct entry into my config file did the trick. Now I just have to configure the rest of the application deployment process.

from shipit-deploy.

@AntJanus OK weird. I close it.

from shipit-deploy.

Yeah, I guess. Well, at least there's an issue open now that anyone with a Windows machine can review in case they encounter the same problem.

from shipit-deploy.

Should be fixed by #49

from shipit-deploy.

@neoziro thanks! I'll have to try this out :)

from shipit-deploy.