-
Notifications
You must be signed in to change notification settings - Fork 492
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
how to run mina deploy with sudo? #86
Comments
Please put "question" label for this thread since I did not have permissions to do it by myself. |
Would anyone happen to have an answer for this? I'm running into a similar issue. It's my first time attempting a Rails deploy, and there seems to be no documentation regarding invoking sudo. |
It is not a good practice - to execute any stuff on production server as a sudo. If it is needed indeed, can you describe your situation better? |
I ended up fixing it by reconfiguring the deploy user on my webserver to act as a sudoer. I have my nginx configuration set to point to /srv/www which is owned by root and requires sudo permissions to do anything in the directory. In hindsight, it was easier for me to add the user to do a |
Any chance to reconfigure your setup? Or maybe I'm wrong on the sudo topic? |
I think I'm going to have to reconfigure in the long run and do proper ownership of the web server by a specific user and allow the deploy user to own all of the applications. I wasn't sure of the ramifications of having the /srv/www directory owned by the deploy user though. It's something I need to do some more research on. |
My usual pattern is |
Ah. This is my first application deploy, so it's a trial by fire for me to figure out the best practices for things like that. Thank you for pointing me in the right direction and helping troubleshoot the above problems. |
I can give you a hint: if you're using sudo more than once in your deploy process, you are probably doing something wrong. |
@rstacruz, what do you think about the |
Is there any option like
of capistrano?
The text was updated successfully, but these errors were encountered: