The repository includes both a Dockerfile and docker-compose.yml.
The Docker build is multi-stage:
- Base:
node:22.14.0-alpine - Copies
package*.json, runsnpm ci
- Base:
node:22.14.0-alpine - Accepts build args:
NEXT_PUBLIC_BASE_URL,NEXT_PUBLIC_CLIENT_ID,NEXT_PUBLIC_GTM_ID - Reuses deps/node_modules from stage 1
- Copies source, builds with
npm run build - Standalone output (
output: "standalone")
- Base:
node:22.14.0-alpine - Non-root user (
app) - Copies standalone, static, public
- Env:
NODE_ENV=production,PORT=4200,HOSTNAME=0.0.0.0,NEXT_TELEMETRY_DISABLED=1 - Exposes
4200 - CMD:
["node", "server.js"]
docker-compose.yml defines web service:
- Build: current dir +
Dockerfile, args:NEXT_PUBLIC_BASE_URLNEXT_PUBLIC_CLIENT_IDNEXT_PUBLIC_GTM_ID:
- Ports:
"4200:4200" - Env:
NODE_ENV=production - Restart:
unless-stopped
From next.config.js:
output: "standalone"compress: trueproductionBrowserSourceMaps: false- ESLint ignored during builds
release-it from npm run release:
- Commits changes
- GitHub releases
- Updates
CHANGELOG.md(conventional commits) - No npm publish
Current version: 1.3.0 (see CHANGELOG.md).
CHANGELOG.md exists and includes at least release 1.2.0 dated 2025-11-20.
The root README.md now links directly to CHANGELOG.md under additional documentation.
The root README.md badges reference GitHub Actions, and renovate.json exists.
A release workflow exists at .github/workflows/release.yml that:
- Triggers on pull request merged to
mainfromdevbranch - Runs
release-itto create releases, update changelog, and tag commits
Deployment triggers, target environment, and full CI pipeline details are not documented here as confirmed facts beyond the release process.
- Prod platform/CI-CD not documented.
- Monitoring/logging/rollback missing.
NEXT_PUBLIC_GTM_IDempty in compose.