You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to setup vault-ai within a docker container, and I'm able to install everything with latest Go, Node v19, poppler.
After resolving the "source" issue mentioned here, I progressed to the actual install, start, and run commands. With two docker terminals running, one is listening on :8100 and the other is running npm run dev. However when I visit http://localhost:8100, I get a problem loading the page.
This seems like a similar issue from this comment.
This is the output of my npm run dev:
> vault-web-server@1.0.0 dev
> webpack --progress --watch
assets by status 1.31 MiB [emitted]
asset bundle.js 1.18 MiB [emitted] (name: app)
asset vendors-node_modules_react-dropzone_dist_es_index_js-node_modules_uuid_dist_esm-browser_v4_js.bundle.js 133 KiB [emitted] [compared for emit] (id hint: vendors)
asset components_Pages_LandingPage_index_jsx.bundle.js 105 KiB [compared for emit]
asset vendors-node_modules_react-router-dom_es_Link_js-node_modules_url-parse_index_js-node_modules-b6a711.bundle.js 35.9 KiB [compared for emit] (id hint: vendors)
asset components_Header_index_jsx.bundle.js 24 KiB [compared for emit]
orphan modules 42 KiB [orphan] 27 modules
runtime modules 7.01 KiB 11 modules
modules by path ./node_modules/ 1.19 MiB 80 modules
modules by path ./components/ 93.9 KiB
modules by path ./components/*.less 22.8 KiB 6 modules
modules by path ./components/Util/*.jsx 7.81 KiB 4 modules
modules by path ./components/Pages/LandingPage/ 20.7 KiB 3 modules
modules by path ./components/Header/ 8.88 KiB 3 modules
modules by path ./components/Page/ 6.87 KiB 3 modules
modules by path ./components/Footer/ 19.2 KiB 3 modules
modules by path ./components/*.jsx 5.14 KiB
./components/index.jsx 430 bytes [built] [code generated]
./components/routes.jsx 4.72 KiB [built] [code generated]
./components/Go/index.jsx 2.48 KiB [built] [code generated]
webpack 5.80.0 compiled successfully in 1530 ms
Anyone have any tips?
The text was updated successfully, but these errors were encountered:
@bmkuter you don't have to do the two terminal thing – the only purpose the npm run dev command serves is it compiles your static/bundle.js so that once you start the server, the site is serving the compiled javascript code.
I recommend adding a "build": "webpack --progress",
command to your package.json, and then calling that in your dockerfile (RUN npm run build-server), before starting the server.
@bmkuter you don't have to do the two terminal thing – the only purpose the npm run dev command serves is it compiles your static/bundle.js so that once you start the server, the site is serving the compiled javascript code.
I recommend adding a "build": "webpack --progress", command to your package.json, and then calling that in your dockerfile (RUN npm run build-server), before starting the server.
EDIT: It seems that what happened to me was just that some environment variables were not set, and the system didn't tell that - maybe because the messages got lost somehow, after editing package.json?
Anyway, after making a new file that had all the environment variables set directly and using "source" on that file, I managed to launch the server.
I've been trying to setup vault-ai within a docker container, and I'm able to install everything with latest Go, Node v19, poppler.
After resolving the "source" issue mentioned here, I progressed to the actual install, start, and run commands. With two docker terminals running, one is listening on :8100 and the other is running
npm run dev
. However when I visit http://localhost:8100, I get a problem loading the page.This seems like a similar issue from this comment.
This is the output of my
npm run dev
:Anyone have any tips?
The text was updated successfully, but these errors were encountered: