ansible-nodejs-role
ansible-nodejs-role copied to clipboard
nodesource
Ansible Role for Node.js Binary Install
I'm investigating the possibility of using this role to install node, but I can't tell if it's still a good way to proceed. There are a lot of really old...
This fixes this warning: > TASK [nodejs : Install Node.js] ************************************************ > Saturday 19 May 2018 08:22:31 +0000 (0:00:00.596) 0:07:16.018 ********** > [DEPRECATION WARNING]: State 'installed' is deprecated. Using state...
Installing on Ubuntu 14.04, I get ``` TASK [nodesource.node : Install Node.js] *************************************** fatal: [CCAP4]: FAILED! => {"changed": false, "failed": true, "msg": "Could not fetch updated apt files"} ``` on...
The supported OS list in the `README.md` file (trusty & xenial) and on [Ansible Galaxy](https://galaxy.ansible.com/nodesource/node/) (precise & trusty) don't match
This was a bit confusing when we read it, cause of the missing word. Maybe these proposed changes are good, or maybe different changes would be better. Thanks!
When there's already a version of node installed (in my case v0.10.33), it doesn't update the package. If however I manually run `apt-get upgrade` on the server, it presents nodejs...
This makes the 'changed=1' return flag clearer when re-running this role on a server.
Error: TASK [nodesource.node : Install Node.js] *************************************** fatal: [MYDOMAIN.COM]: FAILED! => {"cache_update_time": 1455109514, "cache_updated": true, "changed": false, "failed": true, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\" install 'nodejs=4.2_'' failed: E:...
