Nautilus/ledgerdock
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove frontend npm tuning and keep standard install path

Browse Source
This commit is contained in:
Beda Schmid
2026-03-02 17:31:34 -03:00
parent 8cf3748015
commit 83d6a4f367
4 changed files with 3 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
doc/operations-and-configuration.md
View File

@@ -42,24 +42,9 @@ Tail logs:
docker compose logs -f
```
## Frontend Build Network Resilience
## Frontend Build Baseline
The frontend Dockerfile uses `node:22-slim` by default for improved npm network compatibility on IPv4-only Linux hosts.
The frontend image build supports npm fetch tuning through environment-driven compose build args:
- `NPM_REGISTRY` (default `https://registry.npmjs.org/`)
- `NPM_FETCH_RETRIES` (default `5`)
- `NPM_FETCH_RETRY_MINTIMEOUT` (default `20000`)
- `NPM_FETCH_RETRY_MAXTIMEOUT` (default `120000`)
- `NPM_FETCH_TIMEOUT` (default `300000`)
- `DOCKER_BUILD_NETWORK` (default `default`; set to `host` on Linux hosts when bridge-network npm fetches time out)
If frontend dependency downloads fail with npm `ETIMEDOUT` during `docker compose build`, keep defaults first, then try:
```bash
DOCKER_BUILD_NETWORK=host docker compose build --no-cache frontend
```
The frontend Dockerfile uses `node:22-slim` with a standard `npm ci --no-audit` install step and no npm-specific build tuning flags.
## Authentication Model