尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
A modern, fast, and secure Point of Sale (POS) system built with Next.js, Tailwind CSS, Prisma, and PostgreSQL. Designed for retail and small businesses to manage inventory, process sales, and track expenses effortlessly.檢視完整 README ↗A modern, fast, and secure Point of Sale (POS) system built with Next.js, Tailwind CSS, Prisma, and PostgreSQL. Designed for retail and small businesses to manage inventory, process sales, and track expenses effortlessly.
next-themes.git clone https://github.com/sirrryasir/pos.git
cd pos
bun install
Copy the template and fill it in. env.example documents every variable the
app reads, required and optional:
cp env.example .env
openssl rand -base64 32 # paste into BETTER_AUTH_SECRET
Apply the migrations and seed initial data (including the default Admin account):
bun run db:migrate
bun run db:seed
Default Admin Account:
bun dev
Open http://localhost:3000 in your browser to access the system.
The app is deployed on Vercel, with Postgres hosted separately on Railway.
Set these in Vercel → Project → Settings → Environment Variables, for the Production environment (and Preview, if you use preview deployments):
| Variable | Value |
|---|---|
DATABASE_URL | Railway's public url (DATABASE_PUBLIC_URL in the Railway Variables tab) — Vercel connects from outside Railway's private network |
BETTER_AUTH_SECRET | 32+ random bytes: openssl rand -base64 32. Better Auth refuses to start without it |
BETTER_AUTH_URL | The deployed origin, no trailing slash, e.g. https://your-domain.com |
Everything else in env.example is optional. Notably, no origin allowlist
needs maintaining: Vercel serves the app from its own origin, which both Next
and Better Auth trust automatically.
bun run build runs prisma migrate deploy before next build, so every
deploy applies pending migrations before the code that depends on them goes
live. To add one:
# edit prisma/schema.prisma, then:
npx prisma migrate dev --name describe_the_change
Commit the generated folder under prisma/migrations. Never run
prisma db push against production — it changes the schema without recording
a migration, and the next deploy will not know what happened.
Seeding is deliberately not part of the build. The seed creates
[email protected] / password123, which is fine for a local database and an open
door on a public one. After the first deploy, sign in with it once and
immediately change the password — or create your own owner account and delete
the seeded one.
Management > Users to elevate new accounts to admin status.This project is proprietary and confidential.