From 41b8cb3b61d62c9ed93a4bca5ca05266a11173d5 Mon Sep 17 00:00:00 2001 From: A Holt Date: Sat, 14 Jul 2018 14:01:20 -0400 Subject: [PATCH] Update main.yml --- roles/sugarizer/tasks/main.yml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/roles/sugarizer/tasks/main.yml b/roles/sugarizer/tasks/main.yml index 87171e88e..9f98df0a4 100644 --- a/roles/sugarizer/tasks/main.yml +++ b/roles/sugarizer/tasks/main.yml @@ -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)