build: pin outputFileTracingRoot so standalone lands at .next/standalone/server.js

Author: divyamohan1993

Dockerfile

@@ -24,10 +24,7 @@ ENV NEXT_TELEMETRY_DISABLED=1
 ENV PORT=8080
 ENV HOSTNAME=0.0.0.0
 RUN addgroup --system --gid 1001 nodejs && adduser --system --uid 1001 nextjs
-# Next.js 16 standalone output places the runtime under
-# `.next/standalone/sentinelcloud/web/` when the build context is the repo root.
-# We flatten that here so the entrypoint stays `node server.js`.
-COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone/sentinelcloud/web/ ./
+COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
 COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
 COPY --from=builder --chown=nextjs:nodejs /app/public ./public
 USER nextjs

web/next.config.ts

@@ -24,6 +24,11 @@ const securityHeaders = [
 
 const nextConfig: NextConfig = {
   output: 'standalone',
+  // Pin the standalone tracing root to the web directory so the artefact
+  // always lands at .next/standalone/server.js. Without this, Next 16's
+  // workspace detection can place the artefact under nested folders that
+  // depend on the absolute path of the build host.
+  outputFileTracingRoot: __dirname,
   poweredByHeader: false,
   reactStrictMode: true,
   experimental: { serverActions: { bodySizeLimit: '2mb' } },