尚未检测到更新。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.