Merge branch 'canary' into landing_page

Author: aXenDeveloper

.env.example

@@ -1,4 +1,3 @@
-LOGIN_TOKEN_SECRET=vitnode_secret
 POSTGRES_URL=postgresql://root:root@localhost:5432/vitnode
 
 NEXT_PUBLIC_BACKEND_URL=http://localhost:3000

.github/docs/prd.md

@@ -120,6 +120,9 @@ VitNode is designed for individual developers and small teams who need a structu
   - Component scaffolding
   - API endpoint generation
   - Database schema generation from models
+- Logging system with structured logs:
+  - Log levels (debug, info, warn, error)
+  - Contextual logging with request/response metadata
 
 ### File Management
 

.github/workflows/build-lint-test.yml

@@ -22,7 +22,7 @@ jobs:
       - uses: pnpm/action-setup@v4
         name: Install pnpm
         with:
-          version: 10.12.1
+          version: 10.12.4
 
       - name: Install Node.js
         uses: actions/setup-node@v4

.github/workflows/bump_publish.yml

@@ -52,7 +52,7 @@ jobs:
       - uses: pnpm/action-setup@v4
         name: Install pnpm
         with:
-          version: 10.12.1
+          version: 10.12.4
 
       - name: Install Node.js
         uses: actions/setup-node@v4

.vscode/settings.json

@@ -1,5 +1,5 @@
 {
-  "cSpell.words": ["vitnode"],
+  "cSpell.words": ["sonner", "vitnode"],
   "github.copilot.chat.commitMessageGeneration.instructions": [
     {
       "text": "Follow the Conventional Commits format strictly for commit messages. Use the structure below:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n```\n\nGuidelines:\n\n1. **Type and Scope**: Choose an appropriate type (e.g., `feat`, `fix`, `refactor`, `docs`) and optional scope to describe the affected module or feature.\n\n2. **Gitmoji**: Include a relevant `gitmoji` that best represents the nature of the change.\n\n3. **Description**: Write a concise, informative description in the header; use backticks if referencing code or specific terms.\n\nCommit messages should be clear, informative, and professional, aiding readability and project tracking."

apps/docs/content/docs/dev/auth.mdx …ps/docs/content/docs/dev/config/auth.mdxapps/docs/content/docs/dev/auth.mdx renamed to apps/docs/content/docs/dev/config/auth.mdx apps/docs/content/docs/dev/auth.mdx renamed to apps/docs/content/docs/dev/config/auth.mdx

@@ -13,9 +13,7 @@ You can configure the authentication settings in the `VitNodeAPI` function and `
 
 For example you can change the expiration time of the cookie:
 
-import { TypeTable } from 'fumadocs-ui/components/type-table';
-
-```ts title="src/app/api/[...route]/route.ts"
+```ts title="src/vitnode.api.config.ts"
 VitNodeAPI({
   app,
   plugins: [],
@@ -28,6 +26,8 @@ VitNodeAPI({
 });
 ```
 
+import { TypeTable } from 'fumadocs-ui/components/type-table';
+
 ### Options
 
 <TypeTable

apps/docs/content/docs/dev/config/meta.json

@@ -0,0 +1,4 @@
+{
+  "title": "Config",
+  "pages": ["..."]
+}

apps/docs/content/docs/dev/config/rate-limiter.mdx

@@ -0,0 +1,57 @@
+---
+title: Rate Limiter
+description: Stop brute-force attacks and abuse with rate limiting.
+---
+
+Rate limiting is a powerful feature that helps protect your API from abuse and brute-force attacks. It allows you to limit the number of requests a client can make within a specified time frame.
+
+## Usage
+
+```ts title="src/vitnode.api.config.ts"
+export const vitNodeApiConfig = buildApiConfig({
+  // [!code ++:4]
+  rateLimiter: {
+    points: 40,
+    duration: 60,
+  },
+});
+```
+
+### Options
+
+import { TypeTable } from 'fumadocs-ui/components/type-table';
+
+<TypeTable
+  type={{
+    points: {
+      description:
+        'The number of requests allowed within the specified duration.',
+      type: 'number',
+      default: '80 (120 in dev)',
+    },
+    duration: {
+      description:
+        'The time window in seconds during which the requests are counted.',
+      type: 'number',
+      default: '60',
+    },
+    execEvenly: {
+      description:
+        'If true, the requests are distributed evenly over the duration. If false, the requests are counted in a sliding window.',
+      type: 'boolean',
+      default: 'false',
+    },
+    execEvenlyMinDelayMs: {
+      description:
+        'The minimum delay in milliseconds between requests when execEvenly is true.',
+      type: 'number',
+      default: 'duration * 1000 / points',
+    },
+    blockDuration: {
+      description:
+        'The duration in seconds for which the client is blocked after exceeding the rate limit.',
+      type: 'number',
+      default: '0',
+    },
+  }}
+/>

apps/docs/content/docs/dev/database/pagination.mdx

@@ -127,18 +127,13 @@ On the frontend, the pagination system works seamlessly with the DataTable compo
 When fetching data from the API, include the pagination parameters in your request:
 
 ```tsx
+const query = await searchParams; // Assume searchParams is a Promise from the Next.js page context
 const res = await fetcher(userModule, {
   path: '/users',
   method: 'get',
   module: 'user',
   args: {
-    query: {
-      cursor: searchParams.cursor,
-      first: searchParams.first,
-      last: searchParams.last,
-      order: searchParams.order,
-      orderBy: searchParams.orderBy,
-    },
+    query,
   },
   withPagination: true, // Important flag for pagination
 });

apps/docs/content/docs/dev/deployments/cloud/meta.json

@@ -0,0 +1,4 @@
+{
+  "title": "Cloud",
+  "pages": ["..."]
+}