尚未偵測到更新。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.