Closed mcblum closed 7 years ago
Have you tried specifying a path to your gulpfile using the --gulpfile
flag?
cc @sttk btw, I believe this behavior is coming from http://github.com/js-cli/fined
@tkellen I have not. I believe that js-liftoff is being pulled in as part of Webpack or maybe our Gulp component generators, so I'm not invoking it directly. If the task I'm running is gulp webpack
which packages our files for deploy, would would I pass a path directly to a dependency?
Thank you for you assistance on this!
Try running gulp --gulpfile /path/to/gulpfile webpack
@tkellen fined doesn't use findup-sync. gulp-cli (liftoff) uses it to find gulpfile.js
(configPath
) and gulp's package.json
(modulePackage
) and these findings don't use fined.
@tkellen I tried specifying the exact path and still got:
DEBUG [68fdcc3b] /usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:283
if (this.strict) throw er
^
Error: EACCES: permission denied, scandir '/home'
at Error (native)
at Object.fs.readdirSync (fs.js:951:18)
at GlobSync._readdir (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:239:41)
at GlobSync._processReaddir (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:109:22)
at GlobSync._process (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:105:10)
at new GlobSync (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:43:10)
at Function.globSync [as sync] (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/node_modules/glob/sync.js:22:10)
at /usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/lib/findup-sync.js:31:19
at Array.map (native)
at module.exports (/usr/lib/node_modules/gulp/node_modules/liftoff/node_modules/findup-sync/lib/findup-sync.js:30:22)
@tkellen I'm not 100% sure what that means. Am I posting in the wrong repo?
Well, after trying 1000 things I finally realized that Gulp was installed globally on the server and simply needed to be updated to 3.9.1. I don't know why. Whatever it was, it works now!
Thanks all.
@mcblum glad that fixed it. Going to close this.
Does anyone have any idea how I can indicated to liftoff that /home is protected so it should use /home/username as the route? We're trying to deploy our app and getting stuck at: