-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Doesn't work with Capistrano 3.0.1 #7
Comments
@SkyWriter it could be due to the default options problem highlighted in #2 @moll Can you look at my pull request or at least @webflo's pull request soon to narrow down the scope of possible errors? The pull requests are not that complex to review and aim to solve basic problems that a new user will encounter when trying this gem. We can always refactor the code later after the basic needs are met. Right now without the patches to a new user this nice little gem seems unusable. |
@seantan Thanks for you comment. I'll gladly try to apply your patch to Capistrano 3, see if it works and give some feedback. |
But my honest opinion is that there's been a few changes in Capistrano for the past 3 months, so this gem might as well just lag behind a little bit. |
@SkyWriter Thanks for trying the PRs. Will appreciate your feedback. :) |
@seantan, nope, unfortunately it exercises exactly the same behavior after applying your patch. |
@SkyWriter try setting the following
|
Tons of gratitude to you! Now these were two secret ingredients:
That have made working almost out of the box. It's only that I've had to create shared/deploy directory by hand on a cold deployment. |
Glad to be of help :) I agree pt. 1 should be stated in the README to make it obvious. I didn't notice the need to manually create the rsync_cache though. Not sure whether it's a side effect of me using capistrano-bundler gem. For me, doing
created everything. |
Capistrano 3.0.1
Here's deploy.rb:
production.rb is the following:
On a cold deployment outputs the following:
It seems like it's trying to do git stuff on a server, which it is not supposed to be doing.
The text was updated successfully, but these errors were encountered: