-
Notifications
You must be signed in to change notification settings - Fork 70
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
tty #28
Comments
I don't think it is sending the I think we just need to change line 76 to
Or, if you want more control, Would you be able to give this a try? |
I think I looked into it a bit more and concluded that it requires calling ssh2 with a different command (I can't remember, shell instead of exec?), so I just used a grunt shell wrapper instead and sent the raw command. |
I'm stumped on this problem as well. Is there an example of the work around I can view? |
I used a different grunt plugin - https://github.com/sindresorhus/grunt-shell and configured like this: shell: { |
Cool. I started rewritting the grunt-ssh as grunt-shell commands, like so
Then re-reading your comment again I realised I could just chown the folder so I would not need the sudo at all. So I did that, then switched back to using grunt-ssh, and it works great. Thanks for your help. |
Im trying to sudo a command but I'm getting the 'sudo: sorry, you must have a tty to run sudo' error.
To fix this I can send the -t option with ssh. e.g. ssh -t me@host.com "command".
I notice that there is a 'pty' option in ssh2 (which this uses) and I see the pty option if I use the grunt -v option. But alas, it's not working.
I briefly looked at your code and it looks like it should send the option along the chain, but I'm still getting the error. Does it send this option?
The text was updated successfully, but these errors were encountered: