-
Notifications
You must be signed in to change notification settings - Fork 397
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
sudo: no tty present and no askpass program specified #41
Comments
I can confirm this error message on Ubuntu 14.04 server. You can use the root account on ubuntu as a workaround. |
I had the same error, and am using root as a workaround as well.... but I'd prefer not to... |
You don't need to be root. But create an user and allow him to login with SSH keys and make sudo password less. |
BTW: Since Meteor needs port 80, that's why we need root like permission. But just after we bind to the port, your app will step down to a lower permission group. So, if someone breach into your app, he will have some hard time. |
@arunoda Thank you, that is good to know. |
As @arunoda said, run
And then:
|
@LeCoupa +1 for your solution (it would be a good idea to add this in the readme I guess?) |
@LeCoupa can you send me a PR with this added to the README. Add under this: https://github.com/arunoda/meteor-up#setting-up-a-server |
Actually, I run my meteor app behind an apache server on 80, so I specified PORT: 3000 in my env block. I got all the way to when I think it is starting the server and poof, it requires sudo. I'd prefer not to give my user sudoers at all, and if the port requirement is > 1024, then I don't think it should try to elevate with sudo. I was able to get all the directory perms setup for the scp and file juggles, but this last problem confounds me. I have found this dude, who lets node bind to any lower port, but I don't like that solution either |
Ok i have been trying to get around this for 6 hours, i am stumped guys. I know this an old one, but its still open and it is making my life sad. I edited I am about to just skip mup and try to deploy manually with demeteorizer, not the solution i was hoping for :( |
+1, which is annoying because I have made it work previsouly |
Did you try mupx and follow migration? |
@AWI-Koleok Surely you have moved on, but this worked for me. The instructions on https://github.com/arunoda/meteor-up
Note that this is different from the solution above. |
Fixed setupMongo flag ignore bug.
This error message appears when running "mup setup" on my Mac to setup my Ubuntu linux machine for mup deployment.
I'm using ssh based authentication (which works fine when I open a ssh terminal session from my Mac to the Ubuntu server)
After hours of googling and experimenting with no luck so far, I now must bow my head in shame and ask for some kind advice...
The text was updated successfully, but these errors were encountered: