mirror of
https://github.com/tiennm99/loto.git
synced 2026-10-13 20:15:13 +00:00
tiennm99
594c714527
Two named build scripts replace the prior CF_PAGES auto-detect:
npm run build:gh → BUILD_PROFILE=gh, basePath /loto
target: https://tiennm99.github.io/loto
npm run build:cf → BUILD_PROFILE=cf, basePath ""
target: https://loto.miti99.com (CF Pages custom domain)
Both deploy workflows now use the matching profile script. The legacy
`npm run build` keeps its prior behaviour (defaults to /loto basePath) so
nothing else in the toolchain breaks. NEXT_BASE_PATH still wins for any
one-off custom-domain build.
CF_PAGES auto-detection removed — explicit profiles are clearer than
relying on the host injecting a magic env var, and dashboard users should
just set the build command to `npm run build:cf`.
Lô tô
Bàn số của trò chơi "Lô tô" — Next.js app.
Two pages: / for players, /master for the host (quản trò) — calls numbers, shows a tracking board, and has its own player card to play along.
See docs/ for project overview, architecture, code standards, and deployment.
Development
npm run dev
Inside code-server (reverse proxy)
cp .env.example .env.local
# edit .env.local: set CODESERVER_HOST and CODESERVER_PORT
npm run dev:codeserver
Open https://<CODESERVER_HOST>/absproxy/<CODESERVER_PORT>/.
Use /absproxy/{port}/, not /proxy/{port}/ — the latter strips the path prefix and breaks Next's basePath. HMR may not survive the proxy; refresh manually if it disconnects.
Build
npm run build
Static export to out/. Deployed to GitHub Pages from master via .github/workflows/deploy.yml.