Files
Alem Tuzlak b7e009c56b fix: correct verbose default in docs and remove stray vscode-extension README
The docs table and prose claimed `debug: true` sets `verbose: true`,
but the implementation intentionally defaults verbose to false (PII
safety). Fixed the table and explanatory text to match.

Also removed packages/vscode-extension/README.md which was committed
on this branch by mistake — it describes an unrelated VS Code extension
and has nothing to do with debug mode.
2026-04-15 17:18:09 +02:00
..
2024-10-22 01:57:00 -07:00
2025-12-17 23:01:05 -05:00
2025-03-26 18:57:25 -07:00

fumadocs-test

This is a Next.js application generated with Create Fumadocs.

Run development server:

npm run dev
# or
pnpm dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

Learn More

To learn more about Next.js and Fumadocs, take a look at the following resources:

Vercel Deployment with Git LFS

Docs assets are tracked with Git LFS. To ensure production builds always receive real asset bytes (not pointer files), deploy docs through GitHub Actions using .github/workflows/deploy_docs_vercel.yml.

Required GitHub repository secrets:

  • VERCEL_TOKEN
  • VERCEL_ORG_ID
  • VERCEL_PROJECT_ID_DOCS

PR previews:

  • .github/workflows/deploy_docs_vercel_preview.yml deploys docs previews for non-fork pull requests.
  • The workflow posts/updates a sticky PR comment with a clickable Open Docs Preview link.

Recommended Vercel project setting:

  • Disable automatic Git-based deployments for the docs project and let the GitHub Actions workflow handle production deploys.