# Problème installation environnement de DEV

**URL:** <https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341>\
**Category:** Développement\
**Created:** [Juin 1, 2022, 7:43 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341 "2022-06-01T07:43:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Checconio](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/checconio/32/19810_2.png) [@Checconio](https://community.gladysassistant.com/u/Checconio)\
**Post date:** [Juin 1, 2022, 7:43 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/1 "2022-06-01T07:43:53Z")

</div>

Hello 🙂

Je demande un peu d’aide car je souhaite commencer à regarder pour dev sur Gladys et donc installer l’environnement de DEV.

Je suis la doc du site [Mettre en place un environnement de développement sous Windows | Gladys Assistant](https://gladysassistant.com/fr/docs/dev/setup-development-environment-windows/)

Cependant je rencontre des erreurs au moment de l’installation du backend lors du «&nbsp;npm install&nbsp;»

Voici l’erreur:

```auto
root@DORIAN-PC:~/gladys/server# npm install

> cpu-features@0.0.4 install /root/gladys/server/node_modules/cpu-features
> node buildcheck.js > buildcheck.gypi && node-gyp rebuild

sh: 1: cannot create buildcheck.gypi: Permission denied

> ssh2@1.9.0 install /root/gladys/server/node_modules/ssh2
> node install.js

internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module '/root/gladys/server/node_modules/ssh2/install.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
npm WARN gladys-server@ No description
npm WARN gladys-server@ No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/mocha/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-windows-arm64@0.14.32 (node_modules/esbuild-windows-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-windows-arm64@0.14.32: wanted {"os":"win32","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-windows-64@0.14.32 (node_modules/esbuild-windows-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-windows-64@0.14.32: wanted {"os":"win32","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-windows-32@0.14.32 (node_modules/esbuild-windows-32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-windows-32@0.14.32: wanted {"os":"win32","arch":"ia32"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-sunos-64@0.14.32 (node_modules/esbuild-sunos-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-sunos-64@0.14.32: wanted {"os":"sunos","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-openbsd-64@0.14.32 (node_modules/esbuild-openbsd-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-openbsd-64@0.14.32: wanted {"os":"openbsd","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-netbsd-64@0.14.32 (node_modules/esbuild-netbsd-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-netbsd-64@0.14.32: wanted {"os":"netbsd","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-s390x@0.14.32 (node_modules/esbuild-linux-s390x):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-s390x@0.14.32: wanted {"os":"linux","arch":"s390x"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-riscv64@0.14.32 (node_modules/esbuild-linux-riscv64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-riscv64@0.14.32: wanted {"os":"linux","arch":"riscv64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-ppc64le@0.14.32 (node_modules/esbuild-linux-ppc64le):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-ppc64le@0.14.32: wanted {"os":"linux","arch":"ppc64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-mips64le@0.14.32 (node_modules/esbuild-linux-mips64le):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-mips64le@0.14.32: wanted {"os":"linux","arch":"mips64el"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-arm64@0.14.32 (node_modules/esbuild-linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-arm64@0.14.32: wanted {"os":"linux","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-arm@0.14.32 (node_modules/esbuild-linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-arm@0.14.32: wanted {"os":"linux","arch":"arm"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-linux-32@0.14.32 (node_modules/esbuild-linux-32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-32@0.14.32: wanted {"os":"linux","arch":"ia32"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-freebsd-arm64@0.14.32 (node_modules/esbuild-freebsd-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-freebsd-arm64@0.14.32: wanted {"os":"freebsd","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-freebsd-64@0.14.32 (node_modules/esbuild-freebsd-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-freebsd-64@0.14.32: wanted {"os":"freebsd","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-darwin-arm64@0.14.32 (node_modules/esbuild-darwin-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-darwin-arm64@0.14.32: wanted {"os":"darwin","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-darwin-64@0.14.32 (node_modules/esbuild-darwin-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-darwin-64@0.14.32: wanted {"os":"darwin","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-android-arm64@0.14.32 (node_modules/esbuild-android-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-android-arm64@0.14.32: wanted {"os":"android","arch":"arm64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: esbuild-android-64@0.14.32 (node_modules/esbuild-android-64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-android-64@0.14.32: wanted {"os":"android","arch":"x64"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: cpu-features@0.0.4 (node_modules/cpu-features):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: cpu-features@0.0.4 install: `node buildcheck.js > buildcheck.gypi && node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 2

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ssh2@1.9.0 install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ssh2@1.9.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-06-01T07_31_44_916Z-debug.log

```

J’ai vérifié directement dans les fichiers et le dossier /root/gladys/server/node\_modules/ssh2/ n’existe pas. (j’ai recommencé plusieurs fois de 0 mais pareil)

Y-a-t’il un problème dans le script d’install ?

Merci d’avance 🙂

---

<div class="post-metadata">

**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\
**Post date:** [Juin 1, 2022, 8:15 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/2 "2022-06-01T08:15:34Z")

</div>

`sh: 1: cannot create buildcheck.gypi: Permission denied`

Bizarre que tu sois root, normalement sous wsl tu créé un utilisateur.  
En tout cas c’est l’origine de ton problème

---

<div class="post-metadata">

**Author:** ![Checconio](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/checconio/32/19810_2.png) [@Checconio](https://community.gladysassistant.com/u/Checconio)\
**Post date:** [Juin 1, 2022, 8:37 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/3 "2022-06-01T08:37:47Z")

</div>

Je suis root car je préfère toujours travailler en root 🙂

J’essai avec l’utilisateur classique et je te dit 😉

---

<div class="post-metadata">

**Author:** ![Checconio](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/checconio/32/19810_2.png) [@Checconio](https://community.gladysassistant.com/u/Checconio)\
**Post date:** [Juin 1, 2022, 12:01 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/4 "2022-06-01T12:01:59Z")

</div>

ça m’a l’air tout bon 🙂

je poursuis l’installation merci 😉

---

<div class="post-metadata">

**Author:** ![glasserre](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/g/b5e925/32.png) [@glasserre](https://community.gladysassistant.com/u/glasserre)\
**Post date:** [Octobre 22, 2022, 2:06 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/5 "2022-10-22T14:06:22Z")

</div>

Salut.  
Nouveau PC, je me suis reposé sur le problème que j’avais eu à mettre en place un environnement de DEV pour Gladys.  
Même soucis que @Checconio sauf que j’étais bien avec mon compte utilisateur configuré à l’install de WSL. Puis j’ai du installer tous les modules en erreur lors de l’installe avec sudo npm install [MODULE] (serveur). Bien mettre sudo dans les appels, peut-être il faudrait bien le préciser dans la [doc](https://gladysassistant.com/docs/dev/setup-development-environment-windows/#wsl-configuration) ?  
En tout cas c’est bon, j’ai enfin l’environnement !

---

<div class="post-metadata">

**Author:** ![glasserre](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/g/b5e925/32.png) [@glasserre](https://community.gladysassistant.com/u/glasserre)\
**Post date:** [Octobre 23, 2022, 9:53 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/6 "2022-10-23T21:53:01Z")

</div>

J’ai refait l’installe de l’environnement 2-3 fois :

- Après le git clone, bien mettre son user owner du dossier «&nbsp;gladys&nbsp;» (Ne pas mettre un autre nom de dossier que «&nbsp;gladys&nbsp;», sinon certains fichiers se créent quand même dans le dossier gladys et l’instance ne peut pas fonctionner)

chown -R user gladys

Pour la partie server :

- Se mettre owner sur le dossier node\_module  
chown -R user:user node\_modules/

- Faire sudo npm install  
=\> l’installation de certains modules échouent  
=\> npm install sqlite3  
=\> faire la migration de db  
sudo npm run db-migrate:dev  
=\> Puis sudo npm install node-webcrypto-ossl  
=\> Puis sudo npm install node-broadlink

Le server démarre avec sudo npm start

Pour la partie front :

- Faire npm install, l’installation de cypress échoue  
=\> sudo npm cypress  
=\> sudo npm install

Le front démarre normalement : sudo npm start

Questions :

- A quoi sert Docker Desktop ?
- Quel est le meilleur process à suivre vis-à-vis du repo Git pour au final proposer une PR.  
\*\* J’ai fait un fork de Gladys sur mon compte git.  
\*\* Créer une branche de mon repo pour faire un nouvelle intégration  
\*\* Configurer le repo / branche via VS Code

---

<div class="post-metadata">

**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\
**Post date:** [Octobre 24, 2022, 4:59 UTC](https://community.gladysassistant.com/t/probleme-installation-environnement-de-dev/7341/7 "2022-10-24T04:59:56Z")

</div>

C’est le fait d’installer vos package en sudo qui casse tout, je vais revoir le tuto car ces étapes sont évidemment un contournement