尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证POLCO TOURS is a Tourism Operating System for the Democratic Republic of Congo and Namibia. It combines tour package sales with tourism operations management, connecting tourists, tour operators, guides, drivers, vehicle owners, hotels, restaurants, visa facilitators and other tourism actors on one secure platform.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Tourism Operating System for Namibia and the Democratic Republic of Congo.
This repository is the Phase 0 foundation from the engineering design package
(Volumes 1–11). It establishes the pipeline, database, access control and quality
gates that every later phase builds on.
Stack (DR-001): Next.js (App Router, TypeScript) on Vercel, Neon
PostgreSQL with Prisma, Better Auth + RBAC, DPO Pay (Phase 1).
Launch operator: Lam, holding SUPERADMIN across both countries (DR-005).查看完整 README ↗Tourism Operating System for Namibia and the Democratic Republic of Congo. This repository is the Phase 0 foundation from the engineering design package (Volumes 1–11). It establishes the pipeline, database, access control and quality gates that every later phase builds on.
Stack (DR-001): Next.js (App Router, TypeScript) on Vercel, Neon PostgreSQL with Prisma, Better Auth + RBAC, DPO Pay (Phase 1). Launch operator: Lam, holding SUPERADMIN across both countries (DR-005).
src/modules/*, Vol. 5 §5.2).github/workflows/ci.yml)DATABASE_URL / DIRECT_URL)src/lib/auth.ts, src/lib/rbac.ts)tailwind.config.ts, src/app)prisma/seed.ts, DR-006)src/lib/logger.ts, health probe)tests/rls.cross-tenant.test.ts)The last item is the gate: npm test must pass, which means Row-Level Security
isolates tenants against a real Postgres.
# 1. Install
npm install
# 2. Configure env
cp .env.example .env # fill DATABASE_URL / DIRECT_URL (Neon) + BETTER_AUTH_SECRET
# 3. Create schema, apply RLS policies, seed Lam + tax rates
npm run db:setup # = db:push + db:rls + db:seed
# 4. Finalize Better Auth tables (emits into schema, then push)
npx @better-auth/cli@latest generate
npm run db:push
# 5. Run
npm run dev # http://localhost:3000 (health: /api/v1/health)
| Script | Purpose |
|---|---|
npm run dev / build / start | Next.js dev / production build / serve |
npm run lint / typecheck | ESLint / tsc --noEmit |
npm test / test:watch | Vitest (unit + RLS) |
npm run test:e2e | Playwright smoke |
npm run db:push | Sync Prisma schema to the DB |
npm run db:rls | Apply prisma/rls.sql (RLS policies) |
npm run db:seed | Seed Lam + per-country tax |
npm run db:setup | push + rls + seed in one step |
Note on RLS + migrations:
prisma db push/migratedo not manage Row-Level Security. Always runnpm run db:rlsafter a schema change that adds a tenant-scoped table, and add its policy toprisma/rls.sql.
eu-central-1).DATABASE_URL (host contains
-pooler) and the direct string into DIRECT_URL.DATABASE_URL, DIRECT_URL,
BETTER_AUTH_SECRET, BETTER_AUTH_URL, NEXT_PUBLIC_APP_URL.main → Production; every PR → Preview deployment. Region pinned to fra1
in vercel.json (keep close to the Neon EU region).src/
app/ # Next.js App Router (UI + /api/v1 route handlers)
api/v1/health/ # liveness probe
lib/ # shared kernel: db, auth, rbac, errors, money, audit, logger
modules/ # feature modules (independent, reusable) — Vol. 5 §5.2
auth/ # reference module: domain · repository · service · index
middleware.ts # trace id + locale (rate limit / session hook in Phase 1)
prisma/
schema.prisma # Phase 0 data model
rls.sql # Row-Level Security policies (applied post-push)
seed.ts # Lam operator + superadmin + tax rates
tests/ # Vitest: RLS cross-tenant, RBAC, money
e2e/ # Playwright smoke
docs/decisions/ # DECISION_LOG.md (DR-007 living record)
.github/ # CI workflow + PR template (enforces the DR gate)
Structural or integration changes must add a dated entry to
docs/decisions/DECISION_LOG.md, update the affected volume, and reference the
DR-nnn id in the PR (the template enforces this). See DR-007.