尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Finance platform helper in Germany
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Bilingual Bulgarian/German financial and administrative assistant for people living in Germany. The application helps users understand contracts and official documents, discover relevant benefits and savings opportunities, track deadlines, and prepare next actions in a clear, user-controlled workflow.
Product status: V1 foundation for private customers. The application provides information and document preparation; it is not a tax adviser, lawyer, insurance broker, or official authority.
/bg/... and /de/...)./api/health.| Area | Technology |
|---|---|
| Application | Next.js 16, React 19, TypeScript |
| Styling and UI | Tailwind CSS 4, shadcn/ui primitives, Lucide |
| Internationalization | next-intl, Bulgarian (bg) and German (de) |
| Authentication and data | Supabase Auth, PostgreSQL, Storage, RLS |
| AI and document processing | Groq-compatible AI integration, OCR, PDF.js, Tesseract.js |
| Validation and tests | ESLint, TypeScript, Vitest, repository i18n checks |
| Package manager | pnpm |
| Deployment | Render via GitHub main branch |
pnpm install
cp .env.example .env.local
pnpm dev
Open http://localhost:3000. Bulgarian and German routes are available under /bg and /de.
pnpm build
pnpm start
Copy .env.example to .env.local. Never commit .env.local, service-role credentials, OAuth secrets, or webhook secrets.
| Variable | Required for | Description |
|---|---|---|
NEXT_PUBLIC_SUPABASE_URL | Auth and data | Supabase project URL |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Auth and data | Public Supabase anon key |
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY | Alternative | Public publishable key, where used by the project |
SUPABASE_SECRET_KEY | Server-side operations | Server-only Supabase secret/service key; never expose it to the browser |
NEXT_PUBLIC_DEV_SUPABASE_REDIRECT_URL | Local OAuth | Local callback URL, normally http://localhost:3000/auth/callback |
GROQ_API_KEY | AI features | Server-side AI provider key |
AUTOMATION_WEBHOOK_URL | Offer requests | Automation webhook URL (currently Activepieces Cloud) |
AUTOMATION_WEBHOOK_SECRET | Offer requests | Shared secret used to authenticate webhook delivery |
Public pages and /api/health can run without Supabase configuration. Protected routes and integrations require the relevant variables and return a controlled configuration error when they are unavailable.
| Command | Purpose |
|---|---|
pnpm dev | Start the development server |
pnpm build | Create a production build |
pnpm start | Serve the production build |
pnpm lint | Run ESLint |
pnpm typecheck | Run TypeScript without emitting files |
pnpm test | Run the Vitest suite |
pnpm i18n:verify | Check translation parity, usage, and hardcoded strings |
pnpm supabase:check | Validate the configured Supabase project |
node scripts/terra-preflight.mjs | Check Terra/tool readiness before assigned work |
Recommended pre-commit verification:
pnpm i18n:verify
pnpm typecheck
pnpm lint
pnpm test
app/ Next.js App Router pages and API routes
components/ Shared UI and feature components
i18n/ Locale routing and request configuration
lib/ Domain logic, Supabase helpers, validation, and services
messages/ Bulgarian and German translation dictionaries
public/ PWA assets, icons, and service worker
scripts/ Local validation and readiness scripts
supabase/ Migrations, functions, prepared SQL, and RLS tests
docs/ Product plans, operating notes, and technical scope
proxy.ts Locale and request proxy
Migrations live in supabase/migrations. Apply them through the Supabase CLI in the intended environment; do not edit production tables manually or disable Row Level Security as a shortcut.
supabase link --project-ref <project-ref>
supabase db push
Review migration SQL and RLS policies before applying changes to a shared or production project. The repository also contains prepared SQL and RLS tests that are not automatically applied by the normal migration flow.
The production service is deployed from the GitHub main branch to Render. A normal deployment flow is:
main, according to the repository workflow.Production checks:
curl -i https://vzgplattform.onrender.com/api/health
curl -I https://vzgplattform.onrender.com/bg/auth/login
curl -I https://vzgplattform.onrender.com/de/auth/login
docs/TERRA_START.md — Terra readiness and first-work-package guidancedocs/AUTOMATION_OFFER_REQUEST_PLAN.md — offer-request webhook contract and operating plandocs/AFFILIATE_LAUNCH_PLAN.md — affiliate launch scopedocs/PDF_EXPORT_SCOPE.md — PDF export scopePROJECT_RULES.md — repository safety and implementation rulesAI_WORKFLOW.md — AI-assisted development workflowTreat uploaded documents, financial profiles, authentication data, and extracted facts as sensitive. Keep secrets server-side, use least-privilege Supabase access, preserve RLS policies, validate webhook signatures, and avoid logging customer content or credentials. Changes affecting authentication, database schema, access policies, payments, or production data require an explicit review.
This repository is proprietary and all rights are reserved. No permission is granted to use, copy, modify, publish, distribute, sublicense, or sell any portion of the software without prior written permission from the copyright holder. See LICENSE for the full terms.
VZGplattform / Horizon by VZG provides informational support and document preparation. It does not replace professional tax, legal, insurance, or government advice. Official decisions remain with the competent authorities.