Hugo-Trentesaux
commented
7 years ago Oui, vagrant marche pas bien. Les gens ont abandonné. Mais un bon virtualenv fait l'affaire. J'ai quitté le projet, mais je peux toujours t'aider si tu le souhaites ;) Et je peux t'ajouter au groupe slack, même si je ne sais pas s'il est toujours actif
Le 24 janv. 2017 00:01, Nicolas Iooss notifications@github.com a écrit :
Hello,
As I would like to see what ProjetSigma look like, I am looking forward to build a virtual machine with it. Currently the provided Vagrant configuration file fails in several places and this Pull Request fixes some of them. With it, there is one last failure I do not understand, when running npm install --loglevel=info as user vagrant in /vagrant/frontend:
[22:54:48] Requiring external module ts-node/register TSError: ⨯ Unable to compile TypeScript src/shared/services/api-service.ts (7,23): Cannot find module '../../config'. (2307) src/shared/services/auth-service.ts (3,23): Cannot find module '../../config'. (2307) at getOutput (/vagrant/frontend/node_modules/ts-node/src/ts-node.ts:210:13) at Object.loader (/vagrant/frontend/node_modules/ts-node/src/ts-node.ts:225:23) at Module.load (module.js:357:32) at Function.Module._load (module.js:314:12) at Module.require (module.js:367:17) at require (internal/module.js:20:19) at Liftoff.handleArguments (/vagrant/frontend/node_modules/gulp/bin/gulp.js:116:3) at Liftoff.typings install && gulp check.versions && npm prune npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sigma@1.0.0 postinstall script 'typings install && gulp check.versions && npm prune'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the sigma package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! typings install && gulp check.versions && npm prune npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs sigma npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls sigma npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /vagrant/frontend/npm-debug.log
I do not understand this error so any hint about what would have gone wrong would be appreciated :) Cheers!
You can view, comment on, or merge this pull request online at:
https://github.com/ProjetSigma/provisioning/pull/15
Commit Summary
Use double quote to fill /etc/apt/sources.list.d/nodesource.listFix Django installationapt-get update before installing Node 5Add set -x -e to provisionning script
File Changes
M vagrant_bootstrap.sh (18)
Patch Links:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Hello,
As I would like to see what ProjetSigma look like, I am looking forward to build a virtual machine with it. Currently the provided Vagrant configuration file fails in several places and this Pull Request fixes some of them. With it, there is one last failure I do not understand, when running
npm install --loglevel=infoas uservagrantin/vagrant/frontend:I do not understand this error so any hint about what would have gone wrong would be appreciated :) Cheers!