2017-06-14 2 views
0

Je tente de déployer mon application depuis mon serveur Linux.Déploiement de l'application Angular 2 (sans angular-cli)

Tout fonctionne correctement, sauf que ma commande lite-server ne sert aucun fichier. Accéder à mon serveur à serverUrl:3000 jette un

'site prend trop de temps pour répondre'

Mes scripts de package.json (je lance npm start)

"scripts": { 
    "build": "tsc -p src/", 
    "serve": "lite-server -c=bs-config.json", 
    "prestart": "npm run build", 
    "start": "concurrently \"npm run build:watch\" \"npm run serve\"", 
    "pretest": "npm run build", 
    "test": "concurrently \"npm run build:watch\" \"karma start karma.conf.js\"", 
    "test-once": "karma start karma.conf.js --test-once", 
    "pretest:once": "npm run build", 
    "build:watch": "tsc -p src/ -w", 
    "build:upgrade": "tsc", 
    "serve:upgrade": "http-server", 
    "build:aot": "ngc -p tsconfig-aot.json && rollup -c rollup-config.js", 
    "serve:aot": "lite-server -c bs-config.aot.json", 
    "build:babel": "babel src -d src --extensions \".es6\" --source-maps", 
    "copy-dist-files": "node ./copy-dist-files.js", 
    "i18n": "ng-xi18n", 
    "lint": "tslint ./src/**/*.ts -t verbose" 
    }, 

Mon bs-config.json. Je devais ajouter le "open" : false parce que le lite-serveur a essayé d'ouvrir un navigateur que je ne voulais pas.

{ 
    "server": { 
    "baseDir": "src", 
    "routes": { 
     "/node_modules": "node_modules" 
    } 
    }, "open" : false 
} 

La sortie de cette commande est la suivante:

> [email protected] prestart /home/deploy/home/deploy/frontend 
> npm run build 


> [email protected] build /home/deploy/home/deploy/frontend 
> tsc -p src/ 


> [email protected] start /home/deploy/home/deploy/frontend 
> concurrently "npm run build:watch" "npm run serve" 

[0] 
[0] > [email protected] build:watch /home/deploy/home/deploy/frontend 
[0] > tsc -p src/ -w 
[0] 
[1] 
[1] > [email protected] serve /home/deploy/home/deploy/frontend 
[1] > lite-server -c=bs-config.json 
[1] 
[1] ** browser-sync config ** 
[1] { injectChanges: false, 
[1] files: [ './**/*.{html,htm,css,js}' ], 
[1] watchOptions: { ignored: 'node_modules' }, 
[1] server: 
[1] { baseDir: 'src', 
[1]  middleware: [ [Function], [Function] ], 
[1]  routes: { '/node_modules': 'node_modules' } }, 
[1] open: false } 
[1] [BS] Access URLs: 
[1] ---------------------------------------- 
[1]  Local: http://localhost:3000 
[1]  External: http://serverurl:3000 
[1] ---------------------------------------- 
[1]   UI: http://localhost:3001 
[1] UI External: http://serverurl:3001 
[1] ---------------------------------------- 
[1] [BS] Serving files from: src 
[1] [BS] Watching files... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[1] [BS] Reloading Browsers... 
[0] 9:42:13 AM - Compilation complete. Watching for file changes. 

Tout fonctionne bien quand je lance ceci sur ma machine Windows, mais il les fichiers sont effectivement montré dans la console ainsi. Des idées?

Répondre

0

Il s'avère que mon pare-feu bloquait le port. L'ouverture du port a résolu le problème (ufw allow 3000)