1
0
Fork 0
mirror of https://github.com/iiab/iiab.git synced 2025-03-09 15:40:17 +00:00

Update main.yml

This commit is contained in:
A Holt 2018-07-14 14:01:20 -04:00 committed by GitHub
parent 14efa35628
commit 41b8cb3b61
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -35,6 +35,9 @@
# - 229MB is unfort downloaded to /opt/iiab/sugarizer/.git
# - 1.4MB is unfort downloaded to /opt/iiab/sugarizer-server/.git
# CLARIF: during repeat runs of "./runrole sugarizer", this git sync shows
# "changed" (whereas above git sync shows "ok"). Reason: "npm install"
# (below) modifies /opt/iiab/sugarizer-server/node_modules
- name: Clone llaske/sugarizer-server ({{ sugarizer_server_git_version }}) from GitHub to /opt/iiab
git:
repo: https://github.com/llaske/sugarizer-server
@ -76,9 +79,10 @@
# But For Now: Ubuntu 18.04's apt (approach below) brings in npm 3.5.2,
# which appears suffic "SO FAR"? 18.04's nodejs 8.10.0 is more reassuring!
# Crazy Aside: some versions of npm can upgrade themselves to the latest
# (6.1.0 for now) using command "npm install -g npm", but careful as it
# ends up in /usr/local/bin causing future/pkg management issues:
# CRAZY IDEA: some versions of npm can upgrade themselves to the latest
# (6.1.0 for now) with command "npm install -g npm" if that helps us in
# future, if that helps TK's memory issue etc? If so, be CAREFUL this
# may put npm in /usr/local/bin causing future/pkg management issues:
# https://askubuntu.com/questions/1036278/npm-is-incorrect-version-on-latest-ubuntu-18-04-installation
- name: Install Node.js and npm (ubuntu-18 or not debuntu)