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

nodeProcessCommandLine should be allowed to be a relative path #448

Closed
MrHacky opened this issue Aug 15, 2015 · 4 comments
Closed

nodeProcessCommandLine should be allowed to be a relative path #448

MrHacky opened this issue Aug 15, 2015 · 4 comments

Comments

@MrHacky
Copy link

MrHacky commented Aug 15, 2015

This greatly simplifies deployment for us on our test servers, where a simple unzip of our release package is the only step needed.

See #356 for an implementation. (though that only works if the path starts with '.' as i didn't see an easy way to check if a path is relative...)

@MrHacky MrHacky changed the title nodeProcessCommandLine should still be allowed to be a relative path nodeProcessCommandLine should be allowed to be a relative path Aug 15, 2015
@rramachand21-zz
Copy link
Collaborator

We are not going to support this due to security reasons.

@MrHacky
Copy link
Author

MrHacky commented Sep 1, 2015

Okay... could you please explain what those reasons are?

@RamIdeas
Copy link

RamIdeas commented Nov 5, 2015

Security reasons? Surely being able to specify any .exe anywhere on the file system is more of a security concern

@olee
Copy link

olee commented May 7, 2018

Would like some clarification on this as well?
Where's the problem allowing a path relative to the current directory only like bin\node.exe?
This would work then on different machines as well.

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

4 participants