-
Notifications
You must be signed in to change notification settings - Fork 1
/
log.txt
290 lines (178 loc) · 7.68 KB
/
log.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
npm ERR! path /root/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/root/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-02T06_45_50_831Z-debug.log
npm ERR! path /root/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/root/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-02T09_03_37_009Z-debug.log
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t -n1 kill -9 ; node -r dotenv/config scripts/prod.js
kill -9
Usage:
kill [options] <pid> [...]
Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table
-h, --help display this help and exit
-V, --version output version information and exit
For more details see kill(1).
Creating an optimized production build...
Starting the Production server...
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t -n1 kill -9 ; node -r dotenv/config scripts/prod.js
kill -9
Usage:
kill [options] <pid> [...]
Options:
<pid> [...] send signal to every <pid> listed
-<signal>, -s, --signal <signal>
specify the <signal> to be sent
-l, --list=[<signal>] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table
-h, --help display this help and exit
-V, --version output version information and exit
For more details see kill(1).
Creating an optimized production build...
Starting the Production server...
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t -n1 kill -9 ; node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Starting the Production server...
Compiled successfully.
File sizes after gzip:
47.5 KB build/static/js/main.ebe308d9.js
2.54 KB build/static/css/main.85ffc975.css
The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
serve -s build
Find out more about deployment here:
http://bit.ly/2vY88Kr
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:3002/
Note that the development build is not optimized.
To create a production build, use npm run build.
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t kill -9 && node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Compiled successfully.
File sizes after gzip:
47.5 KB build/static/js/main.ebe308d9.js
2.54 KB build/static/css/main.85ffc975.css
The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
serve -s build
Find out more about deployment here:
http://bit.ly/2vY88Kr
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t kill -9 & node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Starting the Production server...
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & lsof -t -i :7777 | xargs -t kill -9 & node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Starting the Production server...
Compiled successfully.
File sizes after gzip:
47.5 KB build/static/js/main.ebe308d9.js
2.54 KB build/static/css/main.85ffc975.css
The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
serve -s build
Find out more about deployment here:
http://bit.ly/2vY88Kr
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:3002/
Note that the development build is not optimized.
To create a production build, use npm run build.
> [email protected] start /root/apps/Portfolio
> nohup node scripts/build.js & node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Starting the Production server...
Compiled successfully.
File sizes after gzip:
47.5 KB build/static/js/main.ebe308d9.js
2.54 KB build/static/css/main.85ffc975.css
The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
serve -s build
Find out more about deployment here:
http://bit.ly/2vY88Kr
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:3002/
Note that the development build is not optimized.
To create a production build, use npm run build.
> [email protected] start /root/apps/Portfolio
> node scripts/build.js & node -r dotenv/config scripts/prod.js
Creating an optimized production build...
Starting the Production server...
Compiled successfully.
File sizes after gzip:
47.5 KB build/static/js/main.ebe308d9.js
2.54 KB build/static/css/main.85ffc975.css
The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
serve -s build
Find out more about deployment here:
http://bit.ly/2vY88Kr
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:3002/
Note that the development build is not optimized.
To create a production build, use npm run build.
> [email protected] start /root/apps/Portfolio
> lsof -t -i :7777 | xargs -t -n1 kill -9 && node -r dotenv/config scripts/prod.js
> [email protected] start /root/apps/Portfolio
> lsof -t -i :7777 | xargs -t -n1 kill -9 && node -r dotenv/config scripts/prod.js
> [email protected] start /root/apps/Portfolio
> lsof -t -i :7777 | xargs -t -n1 kill -9 ; node -r dotenv/config scripts/prod.js
Starting the Production server...
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:7777/
Note that the development build is not optimized.
To create a production build, use npm run build.
> [email protected] start /root/apps/Portfolio
> lsof -t -i :7777 | xargs -t -n1 kill -9 ; node -r dotenv/config scripts/prod.js
Starting the Production server...
Compiled successfully!
You can now view portfolio in the browser.
http://localhost:7777/
Note that the development build is not optimized.
To create a production build, use npm run build.