moviedo/ansible-role-nvm

Ansible role for using NVM, Node Version Manager, locally.

ansible-role-nvm's Issues

Import Role via Travis CI

Refer to the docs for implementing auto import, to Ansible Galaxy, after Travis CI tests have passed.

Creates check with npm global packages is broken

If the package already exists but with another version then the one we specified it won't be installed (only checked for existing binary but not for version)

Options:

1. Remove this check, and try to reinstall in every run
2. Replace with another check?

@moviedo What do you think?

Ansible warning when run

TASK [moviedo.nvm : NVM | pkgs | install npm module(s)] *****************************************************************************************************************************************************
 [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ nvm_npm_pkgs | length }} > 0

[FEATURE] add support for other shells

Right now, this role only updates the .bashrc

It would be great to support other shells.

This could be done in a couple of ways. One way would be to support a set of known shells.

Another way would be some kind of hook that allows generic .*rc files... harder, but more flexible.

Latest version 1.4.1 broke installations

Since you used vN.N.N until now, and the latest 1.4.1 is in the same syntax, the CLI can't determine which version is the latest, I guess you'll need to remove 1.4.1 and re-release as v1.4.1.

Support for RHEL/Amazon Linux

Would it be possible to add support for RHEL and Amazon Linux?

For example the role fails because Amazon Linux cannot use apt-get but requires yum.
And package libssl-dev is not available but the package openssl-devel is available.

User group can be different from user

Hello,

First, thanks for your repository, which is very useful !

I have an issue when using it on my work laptop, where my user (A) does not have a A group but a domain users since I connect via an LDAP. This cause the role to fail because it can't find the associated group.

Is it possible to add a nvm_group which if not indicated, will fallback on nvm_user value ?