Closed Bug 1303155 Opened 9 years ago Closed 9 years ago

ui fails to initialize on clean clone of balrog

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: vjoshi, Unassigned)

Details

Navigating to http://localhost:8080 results in a connection reset after doing a fresh clone of balrog. The node_modules directory cannot be found in ui within the container, unless `npm install` (which exits with https://pastebin.mozilla.org/8910437) is run. Running npm install from outside the container works as usual.
It seems that we just need to wait until npm install finishes on the container (which might take a long time, depending on the connection speeds). It might be a good idea to add this to the beginner's documentation.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.