insforge 1.2.10 → 1.3.0

package/.cursor/rules/cursor-rules.mdc

@@ -1,94 +0,0 @@
----
-description: Instructions building apps with MCP
-globs: *
-alwaysApply: true
----
-
-# InsForge SDK Documentation - Overview
-
-## What is InsForge?
-
-Backend-as-a-service (BaaS) platform providing:
-
-- **Database**: PostgreSQL with PostgREST API
-- **Authentication**: Email/password + OAuth (Google, GitHub)
-- **Storage**: File upload/download
-- **AI**: Chat completions and image generation (OpenAI-compatible)
-- **Functions**: Serverless function deployment
-
-## Installation
-
-### 🚨 CRITICAL: Follow these steps in order
-
-### Step 1: Download Template
-
-Use the `download-template` MCP tool to create a new project with your backend URL and anon key pre-configured.
-
-### Step 2: Install SDK
-
-```bash
-npm install @insforge/sdk@latest
-```
-
-### Step 3: Create SDK Client
-
-You must create a client instance using `createClient()` with your base URL and anon key:
-
-```javascript
-import { createClient } from '@insforge/sdk';
-
-const client = createClient({
-  baseUrl: 'https://your-app.region.insforge.app',  // Your InsForge backend URL
-  anonKey: 'your-anon-key-here'       // Get this from backend metadata
-});
-
-```
-
-**API BASE URL**: Your API base URL is `https://your-app.region.insforge.app`.
-
-## Getting Detailed Documentation
-
-### 🚨 CRITICAL: Always Fetch Documentation Before Writing Code
-
-Before writing or editing any InsForge integration code, you **MUST** call the `fetch-docs` MCP tool to get the latest SDK documentation. This ensures you have accurate, up-to-date implementation patterns.
-
-### Use the InsForge `fetch-docs` MCP tool to get specific SDK documentation:
-
-Available documentation types:
-
-- `"instructions"` - Essential backend setup (START HERE)
-- `"db-sdk"` - Database operations with SDK
-- **Authentication** - Choose based on implementation:
-  - `"auth-components-react"` - Frontend auth for React+Vite (singlepage App)
-  - `"auth-components-react-router"` - Frontend auth for React(Vite+React Router) (Multipage App)
-- `"storage-sdk"` - File storage operations
-- `"functions-sdk"` - Serverless functions invocation
-- `"ai-integration-sdk"` - AI chat and image generation
-
-## When to Use SDK vs MCP Tools
-
-### Always SDK for Application Logic:
-
-- Authentication (register, login, logout, profiles)
-- Database CRUD (select, insert, update, delete)
-- Storage operations (upload, download files)
-- AI operations (chat, image generation)
-- Serverless function invocation
-
-### Use MCP Tools for Infrastructure:
-
-- Project scaffolding (`download-template`) - Download starter templates with InsForge integration
-- Backend setup and metadata (`get-backend-metadata`)
-- Database schema management (`run-raw-sql`, `get-table-schema`)
-- Storage bucket creation (`create-bucket`, `list-buckets`, `delete-bucket`)
-- Serverless function deployment (`create-function`, `update-function`, `delete-function`)
-
-## Important Notes
-
-- Use the right framework-specific component package for production-ready auth
-- SDK returns `{data, error}` structure for all operations
-- Database inserts require array format: `[{...}]`
-- Serverless functions have single endpoint (no subpaths)
-- Storage: Upload files to buckets, store URLs in database
-- AI operations are OpenAI-compatible
-- **EXTRA IMPORTANT**: Use Tailwind CSS 3.4 (do not upgrade to v4). Lock these dependencies in `package.json`

package/frontend/src/features/database/hooks/useFullMetadata.ts

@@ -1,18 +0,0 @@
-import { useQuery } from '@tanstack/react-query';
-import { advanceService } from '../services/advance.service';
-
-export function useFullMetadata(enabled = false) {
-  const { data, isLoading, error, refetch } = useQuery({
-    queryKey: ['database', 'metadata', 'full'],
-    queryFn: () => advanceService.getDatabaseFullMetadata(),
-    staleTime: 5 * 60 * 1000, // Cache for 5 minutes
-    enabled,
-  });
-
-  return {
-    data,
-    isLoading,
-    error,
-    refetch,
-  };
-}

package/test-gemini.sh

@@ -1,35 +0,0 @@
-#!/bin/bash
-
-API_KEY="ik_fff113df777823a0518b8067e4f4f49bb11661904af26b9fda2ac80892b0558c"
-BASE_URL="http://localhost:7130/api"
-
-echo "🧪 Testing Gemini 2.5 Flash Image Model"
-echo "========================================"
-echo ""
-
-# Test 1: Make an AI request
-echo "1️⃣  Sending chat request to Gemini 2.5 Flash..."
-curl -X POST "$BASE_URL/ai/chat/completion" \
-  -H "Content-Type: application/json" \
-  -H "x-api-key: $API_KEY" \
-  -d '{
-    "model": "google/gemini-2.5-flash",
-    "messages": [
-      {
-        "role": "user",
-        "content": "Hello! Just testing the AI integration with a short message."
-      }
-    ]
-  }' \
-  -s | jq '{text: .text, usage: .metadata.usage}'
-
-echo ""
-sleep 2
-
-# Test 2: Check usage stats
-echo "2️⃣  Checking usage stats after AI request..."
-curl -X GET "$BASE_URL/usage/stats?start_date=2025-11-19T00:00:00Z&end_date=2025-11-20T23:59:59Z" \
-  -s | jq '.ai_usage_by_model'
-
-echo ""
-echo "✅ Test completed!"

package/test-usage-admin.sh

@@ -1,57 +0,0 @@
-#!/bin/bash
-
-# Test InsForge Usage API with admin authentication
-BASE_URL="http://localhost:7130/api"
-
-echo "🧪 Testing InsForge Usage API (Admin Auth)"
-echo "==========================================="
-echo ""
-
-# Step 1: Login as admin to get token
-echo "1️⃣  Logging in as admin..."
-LOGIN_RESPONSE=$(curl -X POST "$BASE_URL/auth/login" \
-  -H "Content-Type: application/json" \
-  -d '{
-    "email": "admin@insforge.local",
-    "password": "admin123"
-  }' \
-  -s)
-
-TOKEN=$(echo $LOGIN_RESPONSE | jq -r '.access_token // empty')
-
-if [ -z "$TOKEN" ]; then
-  echo "❌ Login failed. Response:"
-  echo $LOGIN_RESPONSE | jq '.'
-  exit 1
-fi
-
-echo "✅ Logged in successfully"
-echo ""
-
-# Step 2: Test AI usage summary
-echo "2️⃣  Fetching AI usage summary..."
-curl -X GET "$BASE_URL/ai/usage/summary" \
-  -H "Authorization: Bearer $TOKEN" \
-  -s | jq '.'
-
-echo ""
-
-# Step 3: Test AI usage records
-echo "3️⃣  Fetching AI usage records..."
-curl -X GET "$BASE_URL/ai/usage?limit=5&offset=0" \
-  -H "Authorization: Bearer $TOKEN" \
-  -s | jq '.'
-
-echo ""
-
-# Step 4: Test MCP usage
-echo "4️⃣  Fetching MCP usage..."
-curl -X GET "$BASE_URL/usage/mcp?limit=5" \
-  -H "Authorization: Bearer $TOKEN" \
-  -s | jq '.'
-
-echo ""
-
-echo "✅ All admin tests completed!"
-echo ""
-echo "Note: /api/usage/stats requires cloud backend auth (not admin)"

package/test-usage.sh

@@ -1,50 +0,0 @@
-#!/bin/bash
-
-# Test InsForge Usage API
-# This script tests the usage tracking endpoints
-
-BASE_URL="http://localhost:7130/api"
-API_KEY="ik_fff113df777823a0518b8067e4f4f49bb11661904af26b9fda2ac80892b0558c"
-
-echo "🧪 Testing InsForge Usage API"
-echo "================================"
-echo ""
-
-# Test 1: Record MCP Usage
-echo "1️⃣  Recording MCP usage..."
-curl -X POST "$BASE_URL/usage/mcp" \
-  -H "Content-Type: application/json" \
-  -H "x-api-key: $API_KEY" \
-  -d '{
-    "tool_name": "create-table",
-    "success": true
-  }' \
-  -s | jq '.'
-
-echo ""
-sleep 1
-
-# Test 2: Get MCP Usage Records
-echo "2️⃣  Fetching recent MCP usage..."
-curl -X GET "$BASE_URL/usage/mcp?limit=5" \
-  -H "x-api-key: $API_KEY" \
-  -s | jq '.'
-
-echo ""
-sleep 1
-
-# Test 3: Get Usage Stats (requires cloud backend auth - will fail for local)
-echo "3️⃣  Fetching usage stats (requires cloud backend auth)..."
-START_DATE=$(date -u -v-7d +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || date -u -d "7 days ago" +"%Y-%m-%dT%H:%M:%SZ")
-END_DATE=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
-
-echo "   Date range: $START_DATE to $END_DATE"
-echo "   Note: This endpoint requires cloud backend authentication"
-echo ""
-
-curl -X GET "$BASE_URL/usage/stats?start_date=$START_DATE&end_date=$END_DATE" \
-  -H "x-api-key: $API_KEY" \
-  -s | jq '.'
-
-echo ""
-echo "✅ Tests completed!"