From c2afd5d9beffb3f6d5f11919c7f41410289b284b Mon Sep 17 00:00:00 2001 From: A Holt Date: Sun, 15 Jul 2018 18:56:20 -0400 Subject: [PATCH] Update main.yml --- roles/sugarizer/tasks/main.yml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/roles/sugarizer/tasks/main.yml b/roles/sugarizer/tasks/main.yml index ea4398783..e4622d8d4 100644 --- a/roles/sugarizer/tasks/main.yml +++ b/roles/sugarizer/tasks/main.yml @@ -126,19 +126,21 @@ # SOLUTION: Implement '--allow-root --unsafe-perm=true' below, as is critical # for 1st run of sudo-driven 'npm install' especially: # -# ON DEBIAN: npm 5.6.0's --allow-root is sufficient: causing creation of -# /root/.npm cache & lock files to owned by root:root instead of +# ON DEBIAN: npm 5.6.0's --allow-root would be sufficient: causing creation +# of /root/.npm cache & lock files to owned by root:root instead of # iiab-admin:iiab-admin...thus permitting it & IIAB installs to complete! # -# ON RASPBIAN: npm 5.6.0's --unsafe-perm=true is required, so that npm install -# actually finished (in about 5 minutes). +# ON RASPBIAN: npm 5.6.0's --unsafe-perm=true is *required* so that npm +# install actually finished (in about 5 minutes). It's possible we should +# remove --allow-root in favore of --unsafe-perm=true alone. But this needs +# testing on different Linuxes before proceeding. # # CLARIF 1: Something like 'chown -R root:root /root/.npm' would do the job, -# but cannot happen synchronously with the 1st run of 'npm install' (when -# it's needed!) Similar to what --allow-root does on Debian. +# but cannot happen synchronously throughout the 1st run of 'npm install' +# (when it's needed!) Similar to what --allow-root does on Debian. # # CLARIF 2: Ubuntu 18.04 is currently unaffected due to its ancient -# npm 3.5.2, which instead uses /home/iiab-admin/.npm (these remain owned +# npm 3.5.2, which instead uses /home/iiab-admin/.npm (which remains owned # by iiab-admin:iiab-admin, even with '--allow-root', but thankfully still # gets the job done, for now!)