Files
2026-09-04 16:30:37 +08:00
..
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00
2026-09-04 16:30:37 +08:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Docker Deployment

The container runs the Next.js standalone server directly and exposes port 3000. It does not include Nginx.

For development:

docker compose --env-file .env.development up -d --build

For online deployment:

docker compose --env-file .env.production up -d --build

PING_BACKEND_BASE_URL is read at runtime by the Next.js server. NEXT_PUBLIC_PING_WS_BASE_URL is embedded into browser JavaScript during next build, so change it before rebuilding the production image.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.