Aravind 2eab221eff fix: inject linux-musl sharp binaries into build/ to fix 502 on Dokploy ...

build.sh runs npm run build on macOS, so only the host's sharp binary
(darwin-arm64) got traced into the standalone output. The container
runs node:20-alpine (Linux, musl libc), which cannot load that binary
- the server crashed at runtime, causing a 502 even though the docker
build itself succeeded.

npm pack can fetch another platform's prebuilt sharp/libvips tarballs
without an install-time OS check, so build.sh now pulls the
linux-musl x64 and arm64 builds directly into build/node_modules and
drops the now-unused host binary.

2026-07-14 12:41:07 +05:30

build

fix: inject linux-musl sharp binaries into build/ to fix 502 on Dokploy

2026-07-14 12:41:07 +05:30

.dockerignore

fix: stop tracking stray root .next/ build dir, add .dockerignore

2026-07-14 12:34:34 +05:30

.gitignore

fix: stop tracking stray root .next/ build dir, add .dockerignore

2026-07-14 12:34:34 +05:30

build.sh

fix: inject linux-musl sharp binaries into build/ to fix 502 on Dokploy

2026-07-14 12:41:07 +05:30

Dockerfile

fix: run container on port 80 to match Dokploy domain routing (fixes 502)

2026-07-14 11:24:54 +05:30

nginx.conf

fix: run container on port 80 to match Dokploy domain routing (fixes 502)

2026-07-14 11:24:54 +05:30

Description

No description provided

1 GiB

Languages

HTML 49.2%

RouterOS Script 16.5%

JavaScript 15.9%

Rascal 13.2%

CSS 5.2%