insforge 0.3.3 → 1.2.10

package/.claude-plugin/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "insforge-official-marketplace",
+  "owner": {
+    "name": "InsForge Team",
+    "email": "tony.chang@insforge.dev"
+  },
+  "plugins": [
+    {
+      "name": "insforge",
+      "source": "./claude-plugin",
+      "description": "Official InsForge plugin with schema patterns, best practices for database design, RLS policies, and SDK usage examples. Includes patterns for social graphs, multi-tenancy, and complex relationships.",
+      "version": "1.0.0",
+      "author": {
+        "name": "InsForge Team"
+      },
+      "category": "database",
+      "tags": ["insforge", "postgresql", "postgrest", "database", "baas", "backend", "rls", "schema"]
+    }
+  ]
+}

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

@@ -0,0 +1,94 @@
+---
+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/.dockerignore

@@ -1,6 +1,9 @@
 # Dependencies
 node_modules/
 frontend/node_modules/
+auth/node_modules/
+shared-schemas/node_modules/
+backend/node_modules/
 
 # Build outputs
 dist/

package/.env.example

@@ -24,15 +24,28 @@ ACCESS_API_KEY=ik_your-api-key-here-32-chars-minimum
 # Cloud API Host (Optional)
 CLOUD_API_HOST=https://api.insforge.dev
 
-# Storage Configuration
-# For S3 storage (optional - if not set, will use local filesystem)
+
+
+# Storage + Logs Configuration
+# Storage: Set AWS_S3_BUCKET, AWS_REGION + credentials to use S3 (otherwise uses local filesystem)
+# Logs: Set AWS_REGION + credentials to enable CloudWatch logging (otherwise uses file-based logging)
 AWS_S3_BUCKET=
-AWS_REGION=us-east-2
+AWS_REGION=
+AWS_ACCESS_KEY_ID=
+AWS_SECRET_ACCESS_KEY=
+
+# File-based Logs Configuration (used when AWS credentials are not provided)
+# Directory where log files will be stored (defaults to ./logs)
+LOGS_DIR=
+
 
 # OpenRouter Configuration
 # Get your API key from https://openrouter.ai/keys
 OPENROUTER_API_KEY=
 
+# Posthog Configuration (Only needed if running development mode locally)
+VITE_PUBLIC_POSTHOG_KEY=
+
 # OAuth Configuration (Optional)
 # Google OAuth - Get credentials from https://console.cloud.google.com/
 GOOGLE_CLIENT_ID=
@@ -42,8 +55,24 @@ GOOGLE_CLIENT_SECRET=
 GITHUB_CLIENT_ID=
 GITHUB_CLIENT_SECRET=
 
+#Microsoft OAuth - Get credentials from https://portal.azure.com/
+MICROSOFT_CLIENT_ID=
+MICROSOFT_CLIENT_SECRET=
+
+# Discord OAuth - Get credentials from https://discord.com/developers/applications
+DISCORD_CLIENT_ID=
+DISCORD_CLIENT_SECRET=
+
+# LinkedIn OAuth - Get credentials from https://www.linkedin.com/developers/apps
+LINKEDIN_CLIENT_ID=
+LINKEDIN_CLIENT_SECRET=
+
+# X OAuth - Get credentials from https://developer.twitter.com/en/portal/dashboard
+X_CLIENT_ID=
+X_CLIENT_SECRET=
+
 # Multi-tenant Cloud Configuration
 # Below only used through cloud available solution
 DEPLOYMENT_ID=
 PROJECT_ID=
-APP_KEY=
+APP_KEY=

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: 🐛 Bug Report
-description: Create a bug report to help us improve
+description: Report a bug to help us improve
 title: "[Bug]: "
 labels: ["bug", "needs-triage"]
 assignees: []
@@ -7,77 +7,30 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thanks for taking the time to fill out this bug report! Please provide as much detail as possible.
-        
-        **Note**: This template is for bug reports only. For feature requests, questions, or other issues, please use the appropriate template.
-
-  - type: checkboxes
-    id: checks
-    attributes:
-      label: Pre-submission Checklist
-      description: Please complete these checks before submitting
-      options:
-        - label: I have searched existing issues and confirmed this is not a duplicate
-          required: true
-        - label: I have read the contributing guidelines
-          required: true
-        - label: This is a legitimate bug report and not spam or promotional content
-          required: true
+        Thanks for reporting a bug! Fill out what you can - we'll figure out the rest together.
 
   - type: textarea
     id: what-happened
     attributes:
-      label: What happened?
-      description: Describe the bug clearly and concisely
-      placeholder: A clear description of what the bug is
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected Behavior
-      description: What did you expect to happen?
-      placeholder: A clear description of what you expected to happen
+      label: What's the bug?
+      description: Describe what went wrong
+      placeholder: Tell us what happened...
     validations:
       required: true
 
   - type: textarea
     id: steps-reproduce
     attributes:
-      label: Steps to Reproduce
-      description: Please provide detailed steps to reproduce the issue
+      label: How to reproduce
+      description: Steps to trigger the bug (if you know them)
       placeholder: |
-        1. Go to '...'
-        2. Click on '...'
-        3. Scroll down to '...'
-        4. See error
-    validations:
-      required: true
+        1. Do this...
+        2. Then this...
+        3. Bug happens
 
   - type: textarea
     id: environment
     attributes:
-      label: Environment
-      description: Please provide information about your environment
-      placeholder: |
-        - OS: [e.g. Windows 10, macOS 12.0, Ubuntu 20.04]
-        - Browser: [e.g. Chrome 96, Firefox 95, Safari 15]
-        - Version: [e.g. v1.2.3]
-        - Node.js: [e.g. 16.13.0]
-    validations:
-      required: true
-
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots/Logs
-      description: If applicable, add screenshots or error logs to help explain your problem
-      placeholder: Paste screenshots or logs here
-
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional Context
-      description: Add any other context about the problem here
-      placeholder: Any additional information that might be helpful
+      label: Environment (optional)
+      description: What are you running? (OS, browser, version, etc.)
+      placeholder: e.g., macOS, Chrome, Docker, Node 20...

package/.github/ISSUE_TEMPLATE/config.yml

@@ -4,8 +4,8 @@ contact_links:
     url: https://docs.insforge.dev
     about: Check our documentation for common questions and setup guides
   - name: 💬 Discussions
-    url: https://discord.gg/DvBtaEc9Jz
+    url: https://discord.com/invite/MPxwj5xVvW
     about: Ask questions and discuss ideas with the community
   - name: 🆘 Support
-    url: https://discord.gg/DvBtaEc9Jz
+    url: https://discord.com/invite/MPxwj5xVvW
     about: Get help with installation, configuration, and usage

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,5 +1,5 @@
 name: ✨ Feature Request
-description: Suggest an idea or enhancement for this project
+description: Suggest an idea or enhancement
 title: "[Feature]: "
 labels: ["enhancement", "needs-triage"]
 assignees: []
@@ -7,73 +7,20 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thank you for suggesting a new feature! Please provide as much detail as possible.
-        
-        **Note**: This template is for feature requests only. For bug reports, please use the Bug Report template.
-
-  - type: checkboxes
-    id: checks
-    attributes:
-      label: Pre-submission Checklist
-      description: Please complete these checks before submitting
-      options:
-        - label: I have searched existing issues and confirmed this feature hasn't been requested
-          required: true
-        - label: I have read the contributing guidelines
-          required: true
-        - label: This is a legitimate feature request and not spam or promotional content
-          required: true
+        Have an idea? Share it! We'd love to hear what you're thinking.
 
   - type: textarea
-    id: problem-description
+    id: feature-description
     attributes:
-      label: Problem Description
-      description: Is your feature request related to a problem? Please describe.
-      placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+      label: What feature do you want?
+      description: Describe your idea
+      placeholder: I'd like to be able to...
     validations:
       required: true
 
   - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed Solution
-      description: Describe the solution you'd like
-      placeholder: A clear and concise description of what you want to happen
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives Considered
-      description: Describe alternatives you've considered
-      placeholder: A clear and concise description of any alternative solutions or features you've considered
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: How important is this feature to you?
-      options:
-        - Low - Nice to have
-        - Medium - Would be helpful
-        - High - Important for my use case
-        - Critical - Blocking my usage
-    validations:
-      required: true
-
-  - type: textarea
-    id: use-cases
-    attributes:
-      label: Use Cases
-      description: Describe specific use cases for this feature
-      placeholder: |
-        1. As a [user type], I want [goal] so that [benefit]
-        2. When [situation], I need [functionality] because [reason]
-
-  - type: textarea
-    id: additional-context
+    id: why
     attributes:
-      label: Additional Context
-      description: Add any other context, mockups, or examples about the feature request here
-      placeholder: Any additional information, screenshots, mockups, or examples that would help
+      label: Why do you need this?
+      description: What problem does it solve?
+      placeholder: This would help me...

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+## Summary
+
+<!-- Briefly describe what this PR does -->
+
+## How did you test this change?
+
+<!-- Describe how you tested this PR -->

package/.github/workflows/build-image.yml

@@ -62,4 +62,5 @@ jobs:
           build-args: |
             VERSION=${{ github.ref_name }}
             BUILD_DATE=${{ github.event.head_commit.timestamp }}
-            COMMIT_SHA=${{ github.sha }}
+            COMMIT_SHA=${{ github.sha }}
+            VITE_PUBLIC_POSTHOG_KEY=${{ secrets.POSTHOG_KEY }}

package/.github/workflows/e2e.yml

@@ -0,0 +1,63 @@
+name: E2E Tests
+
+on:
+  pull_request:
+    branches: [main, master, develop]
+  workflow_dispatch:
+
+jobs:
+  e2e:
+    name: E2E Tests
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Create .env file
+        run: |
+          cat > .env << EOF
+          POSTGRES_USER=postgres
+          POSTGRES_PASSWORD=postgres
+          POSTGRES_DB=insforge
+          JWT_SECRET=test-secret-key-for-ci-cd-pipeline
+          ADMIN_EMAIL=admin@example.com
+          ADMIN_PASSWORD=test-admin-password-for-ci
+          TEST_API_BASE=http://localhost:7130/api
+          EOF
+
+      - name: Start Docker Compose services
+        run: docker compose up -d
+
+      - name: Wait for PostgreSQL to be ready
+        run: |
+          echo "Waiting for PostgreSQL..."
+          timeout 60 bash -c 'until docker compose exec -T postgres pg_isready -U postgres; do sleep 2; done'
+
+      - name: Wait for InsForge backend to be ready
+        run: |
+          echo "Waiting for InsForge backend..."
+          timeout 120 bash -c 'until curl -f http://localhost:7130/api/health 2>/dev/null; do echo "Waiting..."; sleep 5; done'
+          echo "Backend is ready!"
+
+      - name: Install test dependencies in container
+        run: docker compose exec -T insforge apk add --no-cache bash curl jq
+
+      - name: Run E2E tests
+        run: docker compose exec -T insforge npm run test:e2e
+
+      - name: Show container logs on failure
+        if: failure()
+        run: |
+          echo "=== PostgreSQL logs ==="
+          docker compose logs postgres
+          echo ""
+          echo "=== InsForge backend logs ==="
+          docker compose logs insforge
+          echo ""
+          echo "=== PostgREST logs ==="
+          docker compose logs postgrest
+
+      - name: Cleanup
+        if: always()
+        run: docker compose down -v

package/CHANGELOG.md

@@ -1,3 +1,44 @@
 # Changelog
 
+## [1.2.8](https://github.com/InsForge/InsForge/compare/v1.2.6...v1.2.8) (2025-12-05)
+
+## [1.2.6](https://github.com/InsForge/InsForge/compare/v1.2.4...v1.2.6) (2025-11-22)
+
+## [1.2.4](https://github.com/InsForge/InsForge/compare/v1.2.3...v1.2.4) (2025-11-22)
+
+## [1.2.2](https://github.com/InsForge/InsForge/compare/v1.2.1-e2e...v1.2.2) (2025-11-18)
+
+# [1.2.0](https://github.com/InsForge/InsForge/compare/v1.1.7-Nov13...v1.2.0) (2025-11-15)
+
+## [1.1.2](https://github.com/InsForge/InsForge/compare/v1.1.0-posthog-9...v1.1.2) (2025-10-28)
+
+
+### Bug Fixes
+
+* addressing coderabbit comments ([97dd933](https://github.com/InsForge/InsForge/commit/97dd9339269991955d8c644f88e77efa6c3f6da2))
+* macOS compatibility and AI config cleanup for e2e tests ([2e04d79](https://github.com/InsForge/InsForge/commit/2e04d7920b00a2b19eed1f0aa3072a6ea937f41a))
+* removing package-lock ([9df772d](https://github.com/InsForge/InsForge/commit/9df772dcadd3a91e2fa70507d8f2779f6910d484))
+* removing package-lock ([222dfc1](https://github.com/InsForge/InsForge/commit/222dfc1231504ce8e7d14d5ab79e57c1b00785c7))
+* update the frontend to use the bulk-upsert exising API ([2b9b3b2](https://github.com/InsForge/InsForge/commit/2b9b3b23c4cc2d401781ba5504c54db07bb84af0))
+
+
+### Features
+
+* added tests for ai configs ([2a4e93a](https://github.com/InsForge/InsForge/commit/2a4e93acf145699511bd0ea49e29926f2d585b36))
+* added tests for functions and secrets ([a985f03](https://github.com/InsForge/InsForge/commit/a985f035ffc1c1152999b317cf4e03e0f45ba34e))
+* added tests for logs ([81f7734](https://github.com/InsForge/InsForge/commit/81f7734f3586e03ae2be5694b63d2a3417ae7339))
+* fixed all the tests with correct format ([1242d13](https://github.com/InsForge/InsForge/commit/1242d133efd4398ae672e1e6c71ae1431aa9ba62))
+* fixed secret tests ([5703836](https://github.com/InsForge/InsForge/commit/5703836ecee0ffeb27bfca9b0d785b95e68f1688))
+* updated the backend and the service to update the csv parsing and validating ([e7ffd29](https://github.com/InsForge/InsForge/commit/e7ffd292fd93381ae2eebde17c16e3996241f15c))
+* updated the frontend to display the button and the respective functions ([50613d8](https://github.com/InsForge/InsForge/commit/50613d8d972b88cf28b147bb7a44901c23d77e79))
+
+# [1.1.0](https://github.com/InsForge/InsForge/compare/v1.0.1-ai-2...v1.1.0) (2025-10-11)
+
+
+### Bug Fixes
+
+* typo in docs ([d2a0efc](https://github.com/InsForge/InsForge/commit/d2a0efc56ab77560597dc2ee46c5f8a669fbd71d))
+
+# [1.0.0](https://github.com/InsForge/InsForge/compare/v0.3.3...v1.0.0) (2025-09-29)
+
 # [0.3.0](https://github.com/InsForge/InsForge/compare/v0.2.9-fix...v0.3.0) (2025-09-26)

package/CLAUDE_PLUGIN.md

@@ -0,0 +1,104 @@
+# InsForge Claude Code Plugin
+
+Official plugin for building with InsForge in Claude Code.
+
+## Installation
+
+### Option 1: Install from InsForge Marketplace (Recommended)
+
+In Claude Code, run:
+
+```
+/plugin marketplace add InsForge/InsForge
+```
+
+Then install the plugin:
+
+```
+/plugin install insforge
+```
+
+### Option 2: Install Directly from Repository
+
+```
+/plugin install https://github.com/InsForge/InsForge/claude-plugin
+```
+
+### Option 3: Local Installation (Development)
+
+```bash
+cd ~/.claude-plugins
+git clone https://github.com/InsForge/InsForge.git
+ln -s InsForge/claude-plugin insforge
+```
+
+## What's Included
+
+### Skill: `insforge-schema-patterns`
+
+Automatically activates when designing database schemas. Includes:
+
+- **Social Graph Patterns** - Follows, likes, and social relationships
+- **Junction Tables** - Many-to-many relationships with proper indexes
+- **Nested Comments** - Self-referential hierarchical data
+- **Multi-Tenant Patterns** - Organization-scoped data with RLS
+- **Best Practices** - Foreign keys, indexes, Row Level Security
+
+## Usage
+
+Once installed, the skill automatically loads when relevant:
+
+**Example:**
+```
+You: "I need to build a social media app with follows and likes"
+
+Claude: [Automatically loads insforge-schema-patterns]
+"I'll use the Social Graph pattern from InsForge best practices:
+
+CREATE TABLE follows (
+  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+  follower_id UUID REFERENCES users(id) ON DELETE CASCADE,
+  following_id UUID REFERENCES users(id) ON DELETE CASCADE,
+  created_at TIMESTAMPTZ DEFAULT NOW(),
+  UNIQUE(follower_id, following_id)
+);
+..."
+```
+
+No special commands needed - Claude knows when to use it based on your conversation!
+
+## What Are Skills?
+
+Skills are folders containing instructions and examples that Claude automatically loads when they're relevant to the task. Think of them as giving Claude domain expertise in specific areas.
+
+The `insforge-schema-patterns` skill teaches Claude:
+- Proven database design patterns for common use cases
+- How to write efficient PostgREST queries with the InsForge SDK
+- Best practices for security (RLS policies)
+- Performance optimization (indexes, query patterns)
+
+## Future Skills (Coming Soon)
+
+We're planning to add:
+- `insforge-fullstack-templates` - Complete app templates (Instagram, Todo, Blog)
+- `insforge-edge-functions` - Serverless function recipes
+- `insforge-realtime` - WebSocket and live collaboration patterns
+
+## Contributing
+
+Want to improve the skills or add new ones?
+
+1. Fork the repository
+2. Edit or add skills in `claude-plugin/skills/`
+3. Test locally by installing from your fork
+4. Submit a PR
+
+Skills are just Markdown files with YAML frontmatter - easy to contribute!
+
+## Feedback
+
+Found an issue or have a suggestion? [Open an issue](https://github.com/InsForge/InsForge/issues) or join our [Discord](https://discord.com/invite/MPxwj5xVvW).
+
+## License
+
+MIT - Same as InsForge