7 Commits

Author SHA1 Message Date
NIJAT
a97779fa3b fix: use static export for both CF Pages and Docker
- Set output: 'export' in next.config.ts (creates /out directory)
- Replaced Node.js standalone Dockerfile with nginx serving static files
- Updated docker-compose.yml for nginx (port 80)
- Both CF Pages and Docker now use the same static build
2025-12-29 18:40:07 +04:00
NIJAT
9930abd991 fix: support both static export (CF Pages) and standalone (Docker) builds
- next.config.ts now checks STATIC_EXPORT env var to toggle output mode
- Added pages:build script for Cloudflare Pages to use
- Docker uses default 'npm run build' which creates .next/standalone
- CF Pages should use 'npm run pages:build' which creates out/
2025-12-29 18:34:48 +04:00
NIJAT
40c93ee13e fix: set static export unconditionally for CF Pages build 2025-12-29 18:28:59 +04:00
NIJAT
ae1448fe48 fix: build config for dual Docker/Cloudflare support
- next.config.ts: Auto-detects Cloudflare Pages (CF_PAGES) to use 'export', defaults to 'standalone' for Docker
- wrangler.json: Removed invalid binding for static deploy
- package.json: Added build:static script
2025-12-29 12:53:45 +04:00
NIJAT
a14c565ce0 chore: fix deployment config- Enabled static export in next.config.ts- Added wrangler.json pointing to ./out assets 2025-12-29 12:45:38 +04:00
retrozenith
57a4aca128 feat(docker): add Docker support for containerized deployment
- Add multi-stage Dockerfile with Node.js 20 Alpine
- Add docker-compose.yml for easy deployment
- Add .dockerignore to optimize build context
- Enable standalone output in next.config.ts
- Add Docker deployment documentation to README
- Move Docker support from planned to completed in roadmap

The Dockerfile uses a three-stage build process:
1. deps: Install production dependencies
2. builder: Build Next.js application
3. runner: Minimal production runtime with non-root user

Includes health checks, restart policy, and security best practices.
2025-12-28 12:52:23 +02:00
NIJAT
45ec702e74 Initial Commit 2025-12-24 07:37:01 +04:00