API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 18th, 2019
104
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.57 KB | None | 0 0
raw download clone embed print report
  1. 01/18 03:46 PM (2h)
  2. Sending build context to Docker daemon 2.616MB
  3.  
  4. 01/18 03:46 PM (2h)
  5. Step 1/7 : FROM node:8
  6. 01/18 03:46 PM (2h)
  7. 8: Pulling from library/node
  8. 01/18 03:46 PM (2h)
  9. ---> 55b43107a63d
  10. 01/18 03:46 PM (2h)
  11. Step 2/7 : COPY . .
  12. 01/18 03:46 PM (2h)
  13. ---> 32889a9a462b
  14. 01/18 03:46 PM (2h)
  15. Step 3/7 : RUN yarn install
  16. 01/18 03:46 PM (2h)
  17. ---> Running in c6a29c3d1174
  18. 01/18 03:46 PM (2h)
  19. yarn install v1.12.3
  20. 01/18 03:46 PM (2h)
  21. [1/5] Validating package.json...
  22. 01/18 03:46 PM (2h)
  23. [2/5] Resolving packages...
  24. 01/18 03:46 PM (2h)
  25. [3/5] Fetching packages...
  26. 01/18 03:46 PM (2h)
  27. info fsevents@1.2.4: The platform "linux" is incompatible with this module.
  28. 01/18 03:46 PM (2h)
  29. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
  30. 01/18 03:46 PM (2h)
  31. [4/5] Linking dependencies...
  32. 01/18 03:47 PM (2h)
  33. [5/5] Building fresh packages...
  34. 01/18 03:47 PM (2h)
  35. $ npm run requirements-check
  36. 01/18 03:47 PM (2h)
  37. npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1547837222143-0.8973367426281191/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
  38. 01/18 03:47 PM (2h)
  39. 01/18 03:47 PM (2h)
  40. > dashboard@1.0.0 requirements-check /
  41. 01/18 03:47 PM (2h)
  42. > node check-version.js
  43. 01/18 03:47 PM (2h)
  44. 01/18 03:47 PM (2h)
  45. Done in 56.98s.
  46. 01/18 03:48 PM (2h)
  47. Removing intermediate container c6a29c3d1174
  48. 01/18 03:48 PM (2h)
  49. ---> 5d77d1d967b2
  50. 01/18 03:48 PM (2h)
  51. Step 4/7 : RUN cd frontend && yarn install
  52. 01/18 03:48 PM (2h)
  53. ---> Running in 4c94a0e8c1b7
  54. 01/18 03:48 PM (2h)
  55. yarn install v1.12.3
  56. 01/18 03:48 PM (2h)
  57. [1/5] Validating package.json...
  58. 01/18 03:48 PM (2h)
  59. [2/5] Resolving packages...
  60. 01/18 03:48 PM (2h)
  61. [3/5] Fetching packages...
  62. 01/18 03:48 PM (2h)
  63. info fsevents@1.2.4: The platform "linux" is incompatible with this module.
  64. 01/18 03:48 PM (2h)
  65. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
  66. 01/18 03:48 PM (2h)
  67. [4/5] Linking dependencies...
  68. 01/18 03:48 PM (2h)
  69. warning " > babel-loader@8.0.4" has unmet peer dependency "webpack@>=2".
  70. 01/18 03:48 PM (2h)
  71. [5/5] Building fresh packages...
  72. 01/18 03:48 PM (2h)
  73. Done in 28.84s.
  74. 01/18 03:48 PM (2h)
  75. Removing intermediate container 4c94a0e8c1b7
  76. 01/18 03:48 PM (2h)
  77. ---> c8772f1c92d3
  78. 01/18 03:48 PM (2h)
  79. Step 5/7 : RUN cd server && yarn install
  80. 01/18 03:48 PM (2h)
  81. ---> Running in 2ccd61ba7e12
  82. 01/18 03:48 PM (2h)
  83. yarn install v1.12.3
  84. 01/18 03:48 PM (2h)
  85. [1/5] Validating package.json...
  86. 01/18 03:48 PM (2h)
  87. [2/5] Resolving packages...
  88. 01/18 03:48 PM (2h)
  89. [3/5] Fetching packages...
  90. 01/18 03:49 PM (2h)
  91. info fsevents@1.2.4: The platform "linux" is incompatible with this module.
  92. 01/18 03:49 PM (2h)
  93. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
  94. 01/18 03:49 PM (2h)
  95. [4/5] Linking dependencies...
  96. 01/18 03:49 PM (2h)
  97. warning "graphql-cli > graphql-cli-prepare > graphql-import@0.4.5" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0".
  98. 01/18 03:49 PM (2h)
  99. warning "graphql-cli > graphql-cli-prepare > graphql-static-binding@0.9.3" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0".
  100. 01/18 03:49 PM (2h)
  101. warning "graphql-cli > tmp-graphql-config-extension-openapi > @kbrandwijk/swagger-to-graphql@2.4.3" has incorrect peer dependency "graphql@^0.12.0 || ^0.13.0".
  102. 01/18 03:49 PM (2h)
  103. [5/5] Building fresh packages...
  104. 01/18 03:49 PM (2h)
  105. Done in 17.27s.
  106. 01/18 03:49 PM (2h)
  107. Removing intermediate container 2ccd61ba7e12
  108. 01/18 03:49 PM (2h)
  109. ---> afb692994130
  110. 01/18 03:49 PM (2h)
  111. Step 6/7 : EXPOSE 5000
  112. 01/18 03:49 PM (2h)
  113. ---> Running in 7d0fc20bacbe
  114. 01/18 03:49 PM (2h)
  115. Removing intermediate container 7d0fc20bacbe
  116. 01/18 03:49 PM (2h)
  117. ---> 2ce1bd9b0e0f
  118. 01/18 03:49 PM (2h)
  119. Step 7/7 : ENTRYPOINT [ "yarn", "run", "stg" ]
  120. 01/18 03:49 PM (2h)
  121. ---> Running in 282a44afc109
  122. 01/18 03:49 PM (2h)
  123. Removing intermediate container 282a44afc109
  124. 01/18 03:49 PM (2h)
  125. ---> 953bf32f9a88
  126. 01/18 03:49 PM (2h)
  127. Successfully built 953bf32f9a88
  128. 01/18 03:49 PM (2h)
  129. Successfully tagged registry.now.systems/now/19d9b71df24d4f28387b4e5853c060e6341018bb:latest
  130. 01/18 03:49 PM (2h)
  131. Storing image
  132. 01/18 03:50 PM (2h)
  133. Deploying image
  134. 01/18 03:51 PM (2h)
  135. Container started
  136. 01/18 03:51 PM (2h)
  137. yarn run v1.12.3
  138. 01/18 03:51 PM (2h)
  139. $ run-p dev:server:stg dev:frontend
  140. 01/18 03:51 PM (2h)
  141. $ cd server && npm run dev:stg
  142. 01/18 03:51 PM (2h)
  143. $ cd frontend && npm run start:frontend
  144. 01/18 03:52 PM (2h)
  145. npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1547837519884-0.46606099898180076/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
  146. 01/18 03:52 PM (2h)
  147. npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1547837519870-0.5831436894290114/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
  148. 01/18 03:52 PM (2h)
  149. 01/18 03:52 PM (2h)
  150. > client@0.1.0 start:frontend /frontend
  151. 01/18 03:52 PM (2h)
  152. > cross-env PORT=5000 craco start
  153. 01/18 03:52 PM (2h)
  154. 01/18 03:52 PM (2h)
  155. 01/18 03:52 PM (2h)
  156. > murcul-server@1.0.0 dev:stg /server
  157. 01/18 03:52 PM (2h)
  158. > NODE_ENV=stg nodemon -e ts,graphql -x ts-node index.ts
  159. 01/18 03:52 PM (2h)
  160. 01/18 03:52 PM (2h)
  161. [nodemon] 1.18.9
  162. 01/18 03:52 PM (2h)
  163. [nodemon] to restart at any time, enter `rs`
  164. 01/18 03:52 PM (2h)
  165. [nodemon] watching: *.*
  166. 01/18 03:52 PM (2h)
  167. [nodemon] starting `ts-node index.ts`
  168. 01/18 03:52 PM (2h)
  169. The following changes are being made to your tsconfig.json file:
  170. 01/18 03:52 PM (2h)
  171. - compilerOptions.baseUrl must not be set (absolute imports are not supported (yet))
  172. 01/18 03:52 PM (2h)
  173. - compilerOptions.paths must not be set (aliased imports are not supported)
  174. 01/18 03:52 PM (2h)
  175. 01/18 03:52 PM (2h)
  176. Starting the development server...
  177. 01/18 03:52 PM (2h)
  178. 01/18 03:52 PM (2h)
  179. 🚀 Server ready at http://localhost:3000/api/graphql
  180. 01/18 03:53 PM (2h)
  181. Compiled successfully!
  182. 01/18 03:53 PM (2h)
  183. 01/18 03:53 PM (2h)
  184. You can now view client in the browser.
  185. 01/18 03:53 PM (2h)
  186. 01/18 03:53 PM (2h)
  187. Local: http://localhost:5000/
  188. 01/18 03:53 PM (2h)
  189. On Your Network: http://172.28.0.24:5000/
  190. 01/18 03:53 PM (2h)
  191. 01/18 03:53 PM (2h)
  192. Note that the development build is not optimized.
  193. 01/18 03:53 PM (2h)
  194. To create a production build, use yarn build.
  195. 01/18 03:53 PM (2h)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!