Ops Panel

เจ้าของผลงานเล่าไว้แบบนี้

https://songdee-ops-panel.vercel.app # Ops Panel This workspace contains the Android/Expo tablet app and the responsive fleet web dashboard. ## Run locally Install dependencies in the repository root and in `web/`. Configure the server-only `DATABASE_URL` and `SONGDEE_ADMIN_TOKEN_SECRET` in `web/.env.local`. For a shared database, use the existing server's token secret: it also encrypts stored device credentials, so an arbitrary local secret cannot read them. The secret must contain at least 32 characters. Then start the Next.js dashboard and API: ```sh bun run dev ``` The dashboard opens at `http://localhost:5173` and calls the Next.js `/api/*` routes on that same origin. These routes use Neon through `DATABASE_URL`, just like Vercel. Next.js loads `web/.env.local`; the launcher does not start or reuse the JSON API on port 4000. When the connection points to the Vercel database, local edits affect the same saved fleet and reports. Sign in with the existing database's admin password. Starting locally does not reset it. `SONGDEE_ADMIN_PASSWORD` is only needed to initialize a database that has no saved admin password yet, and must contain 12–128 characters. If the production signing/encryption key is unavailable, the local dashboard can use the deployed API instead. Set `SONGDEE_API_URL=https://songdee-ops-panel.vercel.app` in `web/.env.local` and leave `NEXT_PUBLIC_API_BASE_URL` unset. Next.js proxies `/api/*` to Vercel, so the dashboard uses the live Neon data and existing production login without copying

โดย peuanthinsan · ดูโพสต์ต้นทาง