Skip to content
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

[Question] Why stork-deploy need sudo password? #14

Open
steveluo opened this issue Jul 19, 2017 · 6 comments
Open

[Question] Why stork-deploy need sudo password? #14

steveluo opened this issue Jul 19, 2017 · 6 comments

Comments

@steveluo
Copy link

Hi,

When I use stork-deploy via ssh to another machine, it keeps asking for sudo password. Is there anyway to avoid this ? Or, if I can input the password in the command?

Thanks.

@jjlauer
Copy link
Member

jjlauer commented Jul 19, 2017 via email

@steveluo
Copy link
Author

@jjlauer thanks for the prompt reply.

But where can I find which commands stork is using with sudo permissions?

@jjlauer
Copy link
Member

jjlauer commented Jul 19, 2017 via email

@steveluo
Copy link
Author

Hi @jjlauer ,

Thank you very much. I have successfully deployed my application with passwordless sudo. I will read the source later to know more about this.

By the way, stork is awesome!

@jjlauer
Copy link
Member

jjlauer commented Sep 11, 2017

@steveluo Stork v2.6.0 is out and I kept your question in mind while working on it. I have a rough plan in future versions to really focus in on permissions to get stork's sudo use down to as little as possible. I'd like to shoot for allowing an admin to create the root deploy dir out-of-band (not using stork and as simple as mkdir -p /opt/app) and maybe locking down sudo use to simply restarting daemons (if your deploys have them). Will keep this issue open so I can remember to revisit it later.

@steveluo
Copy link
Author

@jjlauer Thank you for letting me know. Yes, I use sudo to restart the daemons. I'm totally agreed with you that use sudo as little as possible for security reason. Actually, after creating the directory /opt/app, the later deploy operation (extract file, replace old version, copy config files, etc.) needn't sudo anymore, except restarting the daemon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants