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

Custom nvm_dir does not work in protected directories like /opt/nvm out of the box #27

Open
morgangraphics opened this issue Aug 5, 2020 · 0 comments
Assignees

Comments

@morgangraphics
Copy link
Owner

As described in #26 there is a bug where declaring a custom nvm directory location does not work properly out of the box. This is a permissions issues related to the user running the playbook and associations with group(s) or being added to the sudoers file. A temporary workaround is to assign the directory to the specific user until we address things properly with #26.

@morgangraphics morgangraphics self-assigned this Aug 5, 2020
@morgangraphics morgangraphics changed the title Custom nvm_dir does not work in protected directories like /opt/nvm out of the box Custom nvm_dir does not work in protected directories like /opt/nvm out of the box Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant