- Created docker-entrypoint.sh script to properly start Next.js server
- Script explicitly changes to /app directory and runs node server.js
- Updated Dockerfile to copy and use the entrypoint script
- This fixes the "Cannot find module '/server.js'" error
- Makes deployment more robust against container orchestration overrides
The container now has a proper entrypoint that Portainer expects
and correctly starts the Next.js standalone server.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
- Set proper environment variables (NODE_ENV, HOSTNAME, PORT)
- Use ENTRYPOINT and CMD for better container control
- Fix ownership issues with --chown on COPY commands
- Ensure public directory is copied correctly
- Combine user creation commands for efficiency
The container should now start properly with the Next.js standalone server.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
- Updated Gitea workflow to build Next.js instead of Nuxt
- Removed working-directory references to apps/website
- Created Dockerfile for Next.js production builds
- Added standalone output mode to next.config.js for Docker
- Updated build and artifact paths in workflow
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
