-
Notifications
You must be signed in to change notification settings - Fork 124
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.user param not working #79
Comments
Believe you are not passing it in your call strategy_instance = strategy_class_name.constantize.new(self.server_instance.build_dir, self.options.remote, self.options.branch, self.options.commit_message) Any help would be welcome, getting a Could not read from remote repository |
A git deploy is run from the local machine using a local git command to a remote git repository. When you run the command in terminal, it's run using your local user. The deploy user param is for a remote user on a remote server. This isn't used in git deploy as git deploy doesn't push the folders automatically to a server after committing to git. If you'd like to do that, I'd suggest looking into GitHub post-hooks. This doesn't apply (make sense) if you're running your own git-server (not GitHub or a hosted Git service). |
This issue seems to persist. I would need it as described for a deploy via rsync. The console just outputs:
Looking at rsync.rb it should also output the username, if I set one. Any idea for a quick fix? More background information: I'm using |
I had the same issue. Setting |
I fixed my issue with this PR. But it is just for rsync, maybe the other methods will have the same problem. |
@wlduggan's method words! |
Setting deploy.user to root ( yes thats bad ) but it fails anyway,
im unable to get it to use anything different then my OSX username.
How could this be resolved? I need a certain user to be able to deploy and the setting in config.rb is not picked up!
Good to mention Im using Git for deploy
My config is attached on https://gist.github.com/rubytastic/c8feedfe094fba9da4c0
Any thoughts why its not used on git deploy?
The text was updated successfully, but these errors were encountered: