Files
stripstream/next.config.js
Froidefond Julien 8d1f91d636
Some checks failed
Deploy with Docker Compose / deploy (push) Has been cancelled
feat: optimize Docker startup with Next.js standalone output and proper migrations
- Add `output: standalone` to next.config.js for faster cold start
- Rebuild runner stage around standalone bundle (node server.js instead of pnpm start)
- Replace prisma db push with prisma migrate deploy (proper migration workflow)
- Remove npx/pnpm at runtime, use direct binary paths
- Add HOSTNAME=0.0.0.0 for standalone server to listen on all interfaces
- Fix next.config.js not copied in builder stage
- Update README: pnpm instead of yarn, correct ports, full env vars documentation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-11 21:52:49 +01:00

30 lines
644 B
JavaScript

/** @type {import('next').NextConfig} */
const nextConfig = {
output: "standalone",
webpack: (config) => {
config.resolve.fallback = {
...config.resolve.fallback,
fs: false,
};
return config;
},
// Configuration pour améliorer la résolution DNS
serverExternalPackages: ["dns", "pino", "pino-pretty"],
// Optimisations pour Docker dev
turbopack: {
rules: {
"*.svg": {
loaders: ["@svgr/webpack"],
as: "*.js",
},
},
},
// Optimisation du cache en dev
onDemandEntries: {
maxInactiveAge: 25 * 1000,
pagesBufferLength: 2,
},
};
module.exports = nextConfig;