insforge 0.3.3 → 1.3.0

package/docker-init/db/postgresql.conf

@@ -1,17 +1,17 @@
-# PostgreSQL configuration for InsForge
-# Enable logical replication for Logflare
-
-# Listen on all interfaces to allow container connections
-listen_addresses = '*'
-
-# Set WAL level to logical for Logflare replication
-wal_level = logical
-
-# Set max replication slots (needed for logical replication)
-max_replication_slots = 10
-
-# Set max WAL senders
-max_wal_senders = 10
-
-# Shared preload libraries (if needed)
+# PostgreSQL configuration for InsForge
+# Enable logical replication for Logflare
+
+# Listen on all interfaces to allow container connections
+listen_addresses = '*'
+
+# Set WAL level to logical for Logflare replication
+wal_level = logical
+
+# Set max replication slots (needed for logical replication)
+max_replication_slots = 10
+
+# Set max WAL senders
+max_wal_senders = 10
+
+# Shared preload libraries (if needed)
 # shared_preload_libraries = 'pg_stat_statements'

package/docker-init/logs/vector.yml

@@ -0,0 +1,236 @@
+api:
+  enabled: true
+  address: 0.0.0.0:7135
+
+sources:
+  docker_host:
+    type: docker_logs
+    exclude_containers:
+      - insforge-vector
+    include_containers:
+      - insforge
+      - insforge-deno
+      - insforge-postgrest
+      - insforge-postgres
+
+transforms:
+  project_logs:
+    type: remap
+    inputs:
+      - docker_host
+    source: |-
+      .project = "default"
+      .event_message = del(.message)
+      # Remove leading slash from container name if present
+      container = to_string!(del(.container_name))
+      if starts_with(container, "/") {
+          .appname = slice!(container, 1)
+      } else {
+          .appname = container
+      }
+      del(.container_created_at)
+      del(.container_id)
+      del(.source_type)
+      del(.stream)
+      del(.label)
+      del(.image)
+      del(.host)
+      del(.stream)
+
+  router:
+    type: route
+    inputs:
+      - project_logs
+    route:
+      insforge: '.appname == "insforge"'
+      deno: '.appname == "insforge-deno"'
+      rest: '.appname == "insforge-postgrest"'
+      db: '.appname == "insforge-postgres"'
+      realtime: '.appname == "insforge-realtime"'
+  # PostgREST logs with proper parsing
+  rest_logs:
+    type: remap
+    inputs:
+      - router.rest
+    source: |-
+      # .metadata.host = .project
+      # Parse PostgREST log format: DD/Mon/YYYY:HH:MM:SS +ZZZZ: message
+      parsed, err = parse_regex(.event_message, r'^(?P<time>\d{2}/\w{3}/\d{4}:\d{2}:\d{2}:\d{2} [+-]\d{4}): (?P<msg>.*)$')
+
+      if err == null && parsed != null {
+          .event_message = parsed.msg
+          .metadata.level = "info"
+      } else {
+          # If parsing fails, keep original message
+          .metadata.level = "info"
+      }
+  # InsForge logs are structured JSON, parse and handle both request logs and application logs
+  insforge_logs:
+    type: remap
+    inputs:
+      - router.insforge
+    source: |-
+      # Remove the [backend] prefix if present
+      .event_message = replace!(.event_message, r'^\[backend\] ', "")
+
+      req, err = parse_json(.event_message)
+      if err == null {
+          # Set timestamp from log
+          if req.timestamp != null {
+              .timestamp = to_timestamp!(req.timestamp)
+          }
+
+          # Set log level
+          .metadata.level = req.level
+
+          # Check if this is a request log (has duration field)
+          if req.duration != null {
+              # Flatten request log fields to top level
+              .user_agent = req.userAgent
+              .ip = req.ip
+              .method = req.method
+              .path = req.path
+              .protocol = "HTTP/1.1"
+              .status_code = req.status
+              .size = req.size
+              .duration = req.duration
+              # Format as nginx-style log line
+              .event_message = join!([req.method, req.path, to_string!(req.status), to_string!(req.size), req.duration, "-", req.ip, "-", req.userAgent], " ")
+              .log_type = "request"
+          } else {
+              # This is an application log
+              .event_message = join!([req.level, req.message], " - ")
+              .log_type = "application"
+              if req.error != null {
+                  .error = req.error
+              }
+              if req.stack != null {
+                  .stack = req.stack
+              }
+          }
+      }
+  realtime_logs:
+    type: remap
+    inputs:
+      - router.realtime
+    source: |-
+      parsed, err = parse_regex(.event_message, r'^(?P<time>\d+:\d+:\d+\.\d+) \[(?P<level>\w+)\] (?P<msg>.*)$')
+      if err == null {
+          .event_message = parsed.msg
+          .metadata.level = parsed.level
+      }
+  deno_logs:
+    type: remap
+    inputs:
+      - router.deno
+    source: |-
+      parsed, err = parse_regex(.event_message, r'^(?P<time>\d+:\d+:\d+\.\d+) \[(?P<level>\w+)\] (?P<msg>.*)$')
+      if err == null {
+          .event_message = parsed.msg
+          .timestamp = to_timestamp!(parsed.time)
+          .metadata.level = upcase!(parsed.level)
+          # .metadata.host = .project
+      }
+  # Postgres logs with proper parsing
+  db_logs:
+    type: remap
+    inputs:
+      - router.db
+    source: |-
+      # .metadata.host = "db-default"
+      # Parse PostgreSQL log format: YYYY-MM-DD HH:MM:SS.SSS TZ [PID] LEVEL: message
+      parsed, err = parse_regex(.event_message, r'^(?P<time>\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d{3}) (?P<tz>\w+) \[(?P<pid>\d+)\] (?P<level>LOG|ERROR|WARNING|INFO|NOTICE|FATAL|PANIC|STATEMENT|DETAIL): (?P<msg>.*)$')
+
+      if err == null && parsed != null {
+          .metadata.parsed.pid = parsed.pid
+          .metadata.level = upcase!(parsed.level)
+          .event_message = parsed.msg
+
+          # Normalize STATEMENT and DETAIL to appropriate log levels
+          if .metadata.level == "STATEMENT" {
+              .metadata.level = "INFO"
+          }
+          if .metadata.level == "DETAIL" {
+              .metadata.level = "INFO"
+          }
+      } else {
+          # If parsing fails, keep original message and set default severity
+          .metadata.level = "LOG"
+      }
+
+sinks:
+  # File sinks - JSONL format for FileProvider (always enabled)
+  file_insforge:
+    type: 'file'
+    inputs:
+      - insforge_logs
+    path: '/insforge-logs/insforge.logs.jsonl'
+    encoding:
+      codec: 'json'
+  file_deno:
+    type: 'file'
+    inputs:
+      - deno_logs
+    path: '/insforge-logs/function.logs.jsonl'
+    encoding:
+      codec: 'json'
+  file_rest:
+    type: 'file'
+    inputs:
+      - rest_logs
+    path: '/insforge-logs/postgrest.logs.jsonl'
+    encoding:
+      codec: 'json'
+  file_db:
+    type: 'file'
+    inputs:
+      - db_logs
+    path: '/insforge-logs/postgres.logs.jsonl'
+    encoding:
+      codec: 'json'
+
+  # CloudWatch sinks (ignored if AWS_REGION not set)
+  cw_insforge:
+    type: aws_cloudwatch_logs
+    inputs:
+      - insforge_logs
+    region: ${AWS_REGION:-skip}
+    group_name: /insforge/local
+    stream_name: ${HOSTNAME_OVERRIDE:-local}-insforge-vector
+    encoding:
+      codec: json
+    healthcheck:
+      enabled: false
+  cw_rest:
+    type: aws_cloudwatch_logs
+    inputs:
+      - rest_logs
+    region: ${AWS_REGION:-skip}
+    group_name: /insforge/local
+    stream_name: ${HOSTNAME_OVERRIDE:-local}-postgrest-vector
+    encoding:
+      codec: json
+    healthcheck:
+      enabled: false
+  cw_deno:
+    type: aws_cloudwatch_logs
+    inputs:
+      - deno_logs
+    region: ${AWS_REGION:-skip}
+    group_name: /insforge/local
+    stream_name: ${HOSTNAME_OVERRIDE:-local}-function-vector
+    encoding:
+      codec: json
+    healthcheck:
+      enabled: false
+  cw_db:
+    type: aws_cloudwatch_logs
+    inputs:
+      - db_logs
+    region: ${AWS_REGION:-skip}
+    group_name: /insforge/local
+    stream_name: ${HOSTNAME_OVERRIDE:-local}-postgres-vector
+    encoding:
+      codec: json
+    healthcheck:
+      enabled: false

package/docs/README.md

@@ -0,0 +1,44 @@
+# Mintlify Starter Kit
+
+Use the starter kit to get your docs deployed and ready to customize.
+
+Click the green **Use this template** button at the top of this repo to copy the Mintlify starter kit. The starter kit contains examples with
+
+- Guide pages
+- Navigation
+- Customizations
+- API reference pages
+- Use of popular components
+
+**[Follow the full quickstart guide](https://starter.mintlify.com/quickstart)**
+
+## Development
+
+Install the [Mintlify CLI](https://www.npmjs.com/package/mint) to preview your documentation changes locally. To install, use the following command:
+
+```
+npm i -g mint
+```
+
+Run the following command at the root of your documentation, where your `docs.json` is located:
+
+```
+mint dev
+```
+
+View your local preview at `http://localhost:3000`.
+
+## Publishing changes
+
+Install our GitHub app from your [dashboard](https://dashboard.mintlify.com/settings/organization/github-app) to propagate changes from your repo to your deployment. Changes are deployed to production automatically after pushing to the default branch.
+
+## Need help?
+
+### Troubleshooting
+
+- If your dev environment isn't running: Run `mint update` to ensure you have the most recent version of the CLI.
+- If a page loads as a 404: Make sure you are running in a folder with a valid `docs.json`.
+
+### Resources
+- [Mintlify documentation](https://mintlify.com/docs)
+- [Mintlify community](https://mintlify.com/community)

package/docs/agent-docs/real-time.md

@@ -0,0 +1,269 @@
+# InsForge Realtime - Agent Documentation
+
+## Overview
+
+InsForge Realtime enables real-time pub/sub messaging via WebSockets:
+- **Database events**: Emit events when data changes using triggers
+- **Client events**: Clients can publish custom events to each other
+
+## Backend Setup (Raw SQL)
+
+### Step 1: Create Channel Patterns
+
+Define which channels are available:
+
+```sql
+INSERT INTO realtime.channels (pattern, description, enabled)
+VALUES
+  ('orders', 'Global order events', true),
+  ('order:%', 'Order-specific events (order:123, order:456)', true),
+  ('chat:%', 'Chat room events', true);
+```
+
+**Pattern syntax**: Use `:` as separator, `%` as wildcard (SQL LIKE pattern).
+
+### Step 2: Create Triggers for Database Events
+
+**IMPORTANT**: To emit events when database rows change, create a trigger that calls `realtime.publish()`:
+
+```sql
+-- Step 2a: Create the trigger function
+CREATE OR REPLACE FUNCTION notify_order_changes()
+RETURNS TRIGGER AS $$
+BEGIN
+  PERFORM realtime.publish(
+    'order:' || NEW.id::text,    -- channel name
+    TG_OP || '_order',           -- event name: INSERT_order, UPDATE_order, DELETE_order
+    jsonb_build_object(          -- payload (what clients receive)
+      'id', NEW.id,
+      'status', NEW.status,
+      'total', NEW.total
+    )
+  );
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql SECURITY DEFINER;
+
+-- Step 2b: Attach trigger to table
+CREATE TRIGGER order_realtime
+  AFTER INSERT OR UPDATE ON orders
+  FOR EACH ROW
+  EXECUTE FUNCTION notify_order_changes();
+```
+
+### Step 3: Add Access Control (Optional)
+
+**RLS is disabled by default** for the best developer experience. All authenticated and anonymous users can subscribe to any channel and publish messages out of the box.
+
+To restrict access, first enable RLS, then add policies:
+
+#### Step 3a: Enable RLS
+
+```sql
+ALTER TABLE realtime.channels ENABLE ROW LEVEL SECURITY;
+ALTER TABLE realtime.messages ENABLE ROW LEVEL SECURITY;
+```
+
+#### Step 3b: Restrict who can subscribe (SELECT on realtime.channels)
+
+```sql
+-- Only order owner can subscribe to their order channel
+CREATE POLICY "users_subscribe_own_orders"
+ON realtime.channels FOR SELECT
+TO authenticated
+USING (
+  pattern = 'order:%'
+  AND EXISTS (
+    SELECT 1 FROM orders
+    WHERE id = NULLIF(split_part(realtime.channel_name(), ':', 2), '')::uuid
+      AND user_id = auth.uid()
+  )
+);
+```
+
+**Note**: Use `realtime.channel_name()` in subscribe policies to get the actual channel (e.g., `order:123`) since the table only stores patterns (e.g., `order:%`).
+
+#### Step 3c: Restrict who can publish from client (INSERT on realtime.messages)
+
+```sql
+-- Only chat room members can publish messages
+CREATE POLICY "members_publish_chat"
+ON realtime.messages FOR INSERT
+TO authenticated
+WITH CHECK (
+  channel_name LIKE 'chat:%'
+  AND EXISTS (
+    SELECT 1 FROM chat_members
+    WHERE room_id = NULLIF(split_part(channel_name, ':', 2), '')::uuid
+      AND user_id = auth.uid()
+  )
+);
+```
+
+## Frontend SDK
+
+### Setup
+
+```typescript
+import { createClient } from '@insforge/sdk'
+
+const insforge = createClient({
+  baseUrl: 'https://your-project.insforge.app'
+})
+```
+
+### Core Methods
+
+#### connect() - Establish WebSocket connection
+
+```typescript
+await insforge.realtime.connect()
+```
+
+#### subscribe(channel) - Subscribe to a channel
+
+```typescript
+const { ok, error } = await insforge.realtime.subscribe('order:123')
+if (!ok) console.error('Failed:', error?.message)
+```
+
+#### on(event, callback) - Listen for events
+
+```typescript
+// Listen for database-triggered events
+insforge.realtime.on('INSERT_order', (payload) => {
+  console.log('New order:', payload.id, payload.status)
+})
+
+insforge.realtime.on('UPDATE_order', (payload) => {
+  console.log('Order updated:', payload)
+})
+```
+
+#### once(event, callback) - Listen for event once
+
+```typescript
+// Auto-removes after first invocation
+insforge.realtime.once('order_completed', (payload) => {
+  console.log('Order completed:', payload)
+})
+```
+
+#### publish(channel, event, payload) - Send client events
+
+```typescript
+// Must be subscribed to channel first
+await insforge.realtime.publish('chat:room-1', 'new_message', {
+  text: 'Hello!',
+  sender: 'Alice'
+})
+```
+
+#### unsubscribe(channel)
+
+```typescript
+insforge.realtime.unsubscribe('order:123')
+```
+
+#### off(event, callback) - Remove listener
+
+```typescript
+insforge.realtime.off('UPDATE_order', handler)
+```
+
+#### disconnect() - Close connection
+
+```typescript
+insforge.realtime.disconnect()
+```
+
+### Connection Events
+
+```typescript
+insforge.realtime.on('connect', () => console.log('Connected'))
+insforge.realtime.on('disconnect', (reason) => console.log('Disconnected:', reason))
+insforge.realtime.on('connect_error', (err) => console.error('Connection failed:', err))
+insforge.realtime.on('error', ({ code, message }) => console.error('Error:', code, message))
+```
+
+**Error codes**: `UNAUTHORIZED`, `NOT_SUBSCRIBED`, `INTERNAL_ERROR`
+
+### Properties
+
+```typescript
+insforge.realtime.isConnected           // boolean
+insforge.realtime.connectionState       // 'disconnected' | 'connecting' | 'connected'
+insforge.realtime.socketId              // string (when connected)
+insforge.realtime.getSubscribedChannels() // string[]
+```
+
+### Message Metadata
+
+All received messages include a `meta` field:
+
+```typescript
+insforge.realtime.on('UPDATE_order', (payload) => {
+  console.log(payload.meta.messageId)   // UUID
+  console.log(payload.meta.channel)     // 'order:123'
+  console.log(payload.meta.senderType)  // 'system' (trigger) or 'user' (client)
+  console.log(payload.meta.timestamp)   // Date
+
+  // Your payload fields
+  console.log(payload.status)
+})
+```
+
+## Complete Example
+
+**Backend SQL:**
+```sql
+-- 1. Create channel
+INSERT INTO realtime.channels (pattern, description, enabled)
+VALUES ('order:%', 'Order updates', true);
+
+-- 2. Create trigger for database events
+CREATE OR REPLACE FUNCTION notify_order_status()
+RETURNS TRIGGER AS $$
+BEGIN
+  PERFORM realtime.publish(
+    'order:' || NEW.id::text,
+    'status_changed',
+    jsonb_build_object('id', NEW.id, 'status', NEW.status, 'updated_at', NEW.updated_at)
+  );
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql SECURITY DEFINER;
+
+CREATE TRIGGER order_status_trigger
+  AFTER UPDATE ON orders
+  FOR EACH ROW
+  WHEN (OLD.status IS DISTINCT FROM NEW.status)
+  EXECUTE FUNCTION notify_order_status();
+```
+
+**Frontend:**
+```typescript
+await insforge.realtime.connect()
+await insforge.realtime.subscribe(`order:${orderId}`)
+
+// Listen for database-triggered events
+insforge.realtime.on('status_changed', (payload) => {
+  updateUI(payload.status)
+})
+
+// Client can also publish events to the same channel
+await insforge.realtime.publish(`order:${orderId}`, 'customer_viewed', {
+  viewedAt: new Date().toISOString()
+})
+```
+
+## Quick Reference
+
+| Task | How |
+|------|-----|
+| Emit event on DB change | Create trigger calling `realtime.publish(channel, event, payload)` |
+| Client sends event | `insforge.realtime.publish(channel, event, payload)` |
+| Listen for events | `insforge.realtime.on(eventName, callback)` |
+| Listen once | `insforge.realtime.once(eventName, callback)` |
+| Restrict subscribe access | Enable RLS on `realtime.channels`, then add SELECT policy |
+| Restrict client publish | Enable RLS on `realtime.messages`, then add INSERT policy |

package/docs/changelog.mdx

@@ -0,0 +1,119 @@
+---
+title: "Changelog"
+description: "Latest updates and improvements to InsForge"
+---
+
+## December 2025
+
+<AccordionGroup>
+  <Accordion title="Dec 12 - Alipay & New AI Models" icon="rocket">
+    ### Alipay Payment Support
+    Added **Alipay** as an alternative payment method. Users can now pay for InsForge subscriptions without a credit card.
+
+    <img src="/images/changelog/dec-2025/alipay-payment.webp" alt="Alipay payment method option" style={{maxWidth: '90%'}} />
+
+    ### New AI Models
+    Expanded AI model support:
+    - **GPT 5.2** - OpenAI's latest flagship model with enhanced reasoning, longer context windows, and improved instruction following
+    - **DeepSeek V3** - Open-weight model offering strong performance at lower cost, ideal for high-volume workloads
+
+    <img src="/images/changelog/dec-2025/ai-models.webp" alt="AI Integration with new models" style={{maxWidth: '90%'}} />
+  </Accordion>
+  <Accordion title="Dec 11 - Apple Login & Realtime Module" icon="rocket">
+    ### Apple Login
+    **Sign in with Apple** is now available as an OAuth provider. Enable it in your project settings and let users authenticate with their Apple ID. Like other social providers, InsForge Cloud offers shared credentials for quick testing.
+
+    <img src="/images/changelog/dec-2025/apple-login.jpg" alt="Sign in with Apple authentication" style={{maxWidth: '90%'}} />
+
+    ### Realtime Module
+    Build apps with **realtime pub/sub messaging**. Whether you're creating a chat room, multiplayer game, or collaborative document editor, the new Realtime module handles WebSocket connections, channel subscriptions, and message delivery out of the box.
+
+    Key features include:
+    - **Channel patterns** with wildcard support (e.g., `chat:*`, `game:lobby`)
+    - **Webhook integrations** for server-side event processing
+    - **Message history** and delivery analytics
+    - **RLS-based permissions** for secure subscribe and publish operations
+
+    <img src="/images/changelog/dec-2025/realtime-module.jpg" alt="Realtime multiplayer chess game demo" style={{maxWidth: '90%'}} />
+  </Accordion>
+  <Accordion title="Dec 7 - AI Models, MCP Installer & Security Updates" icon="rocket">
+    ### AI Integration
+    Expanded model support with smarter defaults for different use cases.
+
+    - **Gemini 3 Pro** is now the default image generation model.
+    - **Grok 4.1 Fast** added to model selection for quicker, lightweight inference.
+
+    <img src="/images/changelog/dec-2025/ai-integration.png" alt="AI Integration with new models" style={{maxWidth: '90%'}} />
+
+    ### MCP Installer
+    Updated installer experience with a new InsForge-branded startup screen and clearer next-step instructions.
+
+    <img src="/images/changelog/dec-2025/mcp-installer.png" alt="MCP Installer with InsForge branding" style={{maxWidth: '90%'}} />
+
+    ### Security & Framework Updates
+    Updated Next.js version in response to a [security incident](https://nextjs.org/blog/CVE-2025-66478).
+  </Accordion>
+</AccordionGroup>
+
+## November 2025
+
+<AccordionGroup>
+  <Accordion title="Nov 30 - QuickStart, Auth Components & Dashboard Tools" icon="rocket">
+    ### QuickStart Prompts & Templates
+    Get started faster with our new quickstart prompts and templates for common apps. Builders can now start with one click and get a fullstack app running in **5 minutes**.
+
+    <img src="/images/changelog/nov-2025/quickstart-prompts.webp" alt="QuickStart Prompts and Templates" />
+
+    ### Auth Components
+    Drop-in prebuilt React auth components for your app. Get a working auth flow right away with social sign-on support built in by default.
+
+    <img src="/images/changelog/nov-2025/auth-components.webp" alt="Auth Components with Social Sign-on" />
+
+    ### Database Metadata Dashboard
+    View your RLS policies, triggers, functions, and indexes all in one place. This makes debugging and understanding your project security much easier.
+
+    <img src="/images/changelog/nov-2025/database-metadata.webp" alt="Database Metadata Dashboard" />
+
+    ### SQL Editor
+    Run SQL queries directly in the InsForge dashboard. No external tools required.
+
+    <img src="/images/changelog/nov-2025/sql-editor.webp" alt="SQL Editor in Dashboard" />
+
+    ### Usage Page
+    A new dashboard section that displays a clear breakdown of your resource usage and what your plan includes.
+
+    <img src="/images/changelog/nov-2025/usage-page.webp" alt="Usage Page Dashboard" />
+  </Accordion>
+</AccordionGroup>
+
+## October 2025
+
+<AccordionGroup>
+  <Accordion title="Oct 30 - OAuth Providers, SDK & Logs" icon="rocket">
+    ### OAuth: 4 New Third-Party Providers
+    You can now enable third-party logins with **LinkedIn, Microsoft, Facebook, and Discord**. On InsForge Cloud, we provide shared credentials for developers who want to quickly test these login flows.
+
+    After enabling, you can implement these logins directly through your agent by sending a simple prompt:
+
+    ```text
+    implement Discord login
+    ```
+
+    <img src="/images/changelog/october-2025/oauth-providers.webp" alt="OAuth Providers - LinkedIn, Microsoft, Facebook, and Discord" />
+
+    ### Import CSV to Your Table
+    You can now upload `.csv` files directly into any table from the dashboard. Perfect for bringing in sample data or migrating from other tools.
+
+    <img src="/images/changelog/october-2025/csv-upload.webp" alt="CSV Upload to Tables Feature" />
+
+    ### InsForge.js SDK
+    We've released our **insforge-js SDK** to make it easier for developers to integrate InsForge into their workflows. Manage auth, query databases, and control your backend programmatically with a few lines of code.
+
+    **Repository:** [GitHub](https://github.com/InsForge/InsForge-sdk-js)
+
+    ### Logs
+    The new logs page lets you monitor container logs in real time. You can watch your backend activity directly in the dashboard, or let AI coding agents query logs through the InsForge MCP to automatically debug and search for errors.
+
+    <img src="/images/changelog/october-2025/logs-feature.webp" alt="Real-time Logs Monitoring Feature" />
+  </Accordion>
+</AccordionGroup>