Skip to content
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

Merge with ssh default port from rainerfrey #13

Closed
wants to merge 5 commits into from

Conversation

mcary
Copy link

@mcary mcary commented Jul 12, 2011

Merge rainerfrey's contribution (the only outstanding contribution with test coverage) into mine and resolve conflicts. Evidently everyone's tweaks all touch the same line: the one with the rsync command.

rainerfrey and others added 5 commits April 19, 2011 20:45
…t default. This causes rsync to honor .ssh/config entries automatically.
When rsync fails, I'm getting a deploy that looks like it went fine
except for an inconspicuous message saying that rsync failed and a
production deployment that's still on the old code version.  Sometimes I
don't notice right away that the new code is not actually live, and this
is a big problem.

I'd like to see a clear error message when rsync fails.

Raise an exception of rsync fails to any of the servers receiving a code
update.
When running rsync, the RsyncWithRemoteCache strategy doesn't heed
Capistrano's :gateway parameter, which says to SSH to the server
named by that parameter before connecting to the target server.

Add support for a gateway by using the ProxyCommand SSH directive.
Assume netcat is installed as nc on the target system.
Conflicts:
	lib/capistrano/recipes/deploy/strategy/rsync_with_remote_cache.rb
        Keep both rainerfrey's and mcary's changes to the rsync command.
@reagent
Copy link
Contributor

reagent commented Oct 17, 2014

This commit addresses the port issue. I'll take a look through the rest of these commits -- there's been enough churn bringing this gem up-to-date, that your PR will no longer apply cleanly to master.

Thanks for submitting this -- sorry for the delay. Better late than never I guess?

@reagent
Copy link
Contributor

reagent commented Oct 21, 2014

I resolved #9 and will address #12 separately -- closing this one out.

@reagent reagent closed this Oct 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants