insforge 0.3.1

package/.prettierignore

@@ -0,0 +1,65 @@
+# Dependencies
+node_modules/
+**/node_modules/
+
+# Build outputs
+dist/
+**/dist/
+build/
+**/build/
+.next/
+**/.next/
+
+# Coverage
+coverage/
+**/coverage/
+
+# Turbo
+.turbo/
+**/.turbo/
+
+# Public assets
+public/
+**/public/
+
+# Lock files
+package-lock.json
+**/package-lock.json
+yarn.lock
+**/yarn.lock
+pnpm-lock.yaml
+**/pnpm-lock.yaml
+
+# Generated files
+*.min.js
+*.min.css
+
+# Logs
+*.log
+
+# IDE
+.vscode/
+.idea/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Environment
+.env
+.env.*
+
+# Git
+.git/
+.gitignore
+
+# File types to ignore
+*.md
+*.yaml
+*.yml
+*.json
+
+# Folders to ignore
+docs/
+examples/
+openapi/

package/.prettierrc

@@ -0,0 +1,9 @@
+{
+  "semi": true,
+  "singleQuote": true,
+  "tabWidth": 2,
+  "trailingComma": "es5",
+  "printWidth": 100,
+  "endOfLine": "lf",
+  "jsxSingleQuote": false
+}

package/CHANGELOG.md

@@ -0,0 +1,3 @@
+# Changelog
+
+# [0.3.0](https://github.com/InsForge/InsForge/compare/v0.2.9-fix...v0.3.0) (2025-09-26)

package/CONTRIBUTING.md

@@ -0,0 +1,126 @@
+# Contributing to InsForge
+
+Thank you for your interest in contributing to InsForge. This guide will help you get started with the contribution process.
+
+## Table of Contents
+- [Code of Conduct](#code-of-conduct)
+- [Project Structure](#project-structure)
+- [Prerequisites](#prerequisites)
+- [Getting Started](#getting-started)
+- [Development Workflow](#development-workflow)
+- [Testing](#testing)
+- [Pull Request Process](#pull-request-process)
+- [Code Style](#code-style)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code.
+
+## Project Structure
+
+The InsForge monorepo is organized as follows:
+
+- `/backend` - Core backend service with Express.js, PostgreSQL, and Better Auth integration
+- `/frontend` - React-based admin dashboard for managing databases, users, and storage
+- `/shared-schemas` - Zod schemas and TypeScript types shared between frontend and backend
+- `/docs` - MCP documemtation
+- `/functions` - Serverless edge functions for custom business logic
+- `docker-compose.yml` - Docker config file to start the project
+
+## Prerequisites
+
+Before you start development, ensure you have the following:
+- [Docker](https://www.docker.com/get-started)
+- [Node.js](https://nodejs.org/) (LTS version recommended)
+
+## Getting Started
+
+1. Fork the repository to your GitHub account
+2. Clone your fork locally:
+   ```bash
+   git clone https://github.com/insforge/insforge.git
+   cd insforge
+   ```
+3. Install Docker
+4. Open Docker App
+5. Install Node.js (LTS version recommended)
+6. Create a .env file from the example:
+   
+   On Unix-based systems:
+   ```bash
+   cp .env.example .env
+   ```
+   
+   On Windows:
+   ```bash
+   copy .env.example .env
+   ```
+7. Run the project
+   ```bash
+   docker compose up
+   ```
+
+## Development Workflow
+
+1. Create a new branch for your changes:
+   ```bash
+   git checkout -b type/description
+   # Example: git checkout -b feat/site-deployment
+   ```
+
+   Branch type prefixes:
+   - `feat/` - New features
+   - `fix/` - Bug fixes
+   - `docs/` - Documentation changes
+   - `refactor/` - Code refactoring
+   - `test/` - Test-related changes
+   - `chore/` - Build process or tooling changes
+
+2. Make your changes following the code style guidelines
+3. Add tests for your changes (see test README for guidelines)
+4. Run the test suite:
+   ```bash
+   npm test:e2e
+   ```
+5. Run linter:
+   ```bash
+   npm run lint
+   ```
+6. Ensure all tests pass and the code is properly formatted
+7. Commit your changes with a descriptive message following the Conventional Commits format:
+   ```
+   type(scope): description
+   
+   [optional body]
+   [optional screenshots / videos]
+   [optional footer(s)]
+   ```
+8. Push your branch to your fork
+9. Open a pull request against the main branch
+
+## Testing
+
+All contributions must include appropriate tests. Follow these guidelines:
+- Write unit tests for new features
+- Ensure all tests pass before submitting a pull request
+- Update existing tests if your changes affect their behavior
+- Follow the existing test patterns and structure
+- Test across different environments when applicable
+
+## Pull Request Process
+
+1. Create a draft pull request early to facilitate discussion
+2. Reference any related issues in your PR description (e.g., 'Closes #123')
+3. Ensure all tests pass and the build is successful
+4. Update documentation as needed
+5. Keep your PR focused on a single feature or bug fix
+6. Be responsive to code review feedback
+
+## Code Style
+
+- Follow the existing code style
+- Use TypeScript types and interfaces effectively
+- Keep functions small and focused
+- Use meaningful variable and function names
+- Add comments for complex logic
+- Update relevant documentation when making API changes

package/Dockerfile

@@ -0,0 +1,27 @@
+FROM node:20-alpine
+
+WORKDIR /app
+
+# Copy only package.json files (not lock files) to avoid platform issues
+COPY package.json ./
+COPY backend/package.json ./backend/
+COPY frontend/package.json ./frontend/
+COPY shared-schemas/package.json ./shared-schemas/
+
+# Install all dependencies - will generate Linux-compatible lock file
+RUN npm install && npm cache clean --force && rm -rf /tmp/*
+
+# Copy source code
+COPY . .
+
+# Build arguments for Vite environment variables
+ARG VITE_API_BASE_URL
+
+# Build frontend with the API URL baked in
+RUN npm run build
+
+# Expose ports
+EXPOSE 7130 7131
+
+# Run migrations and start the backend application
+CMD sh -c "cd backend && npm run migrate:up && cd .. && npm start"

package/GITHUB_OAUTH_SETUP.md

@@ -0,0 +1,49 @@
+# GitHub OAuth Application Setup Guide
+
+This document will guide you through the steps to create and configure a GitHub OAuth application for using GitHub login functionality in your project.
+
+## Step 1: Create a GitHub OAuth Application
+
+1.  **Log in to your GitHub account**.
+2.  Navigate to your developer settings page:
+    *   Click on your profile avatar in the top right corner.
+    *   Select **Settings**.
+    *   In the left sidebar, select **Developer settings**.
+3.  On the Developer settings page, select **OAuth Apps**, then click the **New OAuth App** button.
+
+## Step 2: Fill in Application Information
+
+On the "Register a new OAuth application" page, you need to fill in the following information:
+
+*   **Application name**: Give your application a descriptive name, such as `Insforge Dev Login`.
+*   **Homepage URL**: Your application's homepage URL. In development environment, you can set it to `http://localhost:7130` or your frontend development server address.
+*   **Application description** (optional): Provide a brief description of your application.
+*   **Authorization callback URL**: This is the URL where GitHub will redirect users after authorization. For local development, make sure to set it to:
+    ```
+    http://localhost:7130/api/auth/oauth/github/callback
+    ```
+    **Note**: This URL must exactly match the callback URL configured in your backend service, otherwise the OAuth flow will fail.
+
+After filling in the information, click **Register application**.
+
+## Step 3: Get Client ID and Client Secret
+
+After creating the application, you will be redirected to the application's settings page. Here you can see the **Client ID**.
+
+To get the **Client Secret**, click the **Generate a new client secret** button. GitHub will generate a secret and display it to you.
+
+**Important**: The Client Secret will only be shown once. Please copy it immediately and keep it secure. If you lose it, you will need to generate a new one.
+
+## Step 4: Configure Environment Variables
+
+After obtaining the Client ID and Client Secret, you need to add them to your project's `.env` file. Make sure your `.env` file (or corresponding environment configuration file) contains the following two lines:
+
+```env
+GITHUB_CLIENT_ID=YOUR_GITHUB_CLIENT_ID
+GITHUB_CLIENT_SECRET=YOUR_GITHUB_CLIENT_SECRET
+GITHUB_REDIRECT_URI=http://localhost:7130/api/auth/oauth/github/callback
+```
+
+Replace `YOUR_GITHUB_CLIENT_ID` and `YOUR_GITHUB_CLIENT_SECRET` with the actual values you obtained in the previous step.
+
+After completing the above steps, your application is ready to use GitHub OAuth for user authentication.

package/GOOGLE_OAUTH_SETUP.md

@@ -0,0 +1,148 @@
+# Google OAuth Login Setup Guide
+
+## Overview
+
+This project has integrated Google OAuth login functionality, supporting user authentication through Google accounts.
+
+## Environment Variable Configuration
+
+Add the following configuration to your `.env` file:
+
+```env
+# Google OAuth Configuration
+GOOGLE_CLIENT_ID=your_google_client_id
+GOOGLE_CLIENT_SECRET=your_google_client_secret
+GOOGLE_REDIRECT_URI=http://localhost:7130/api/oauth/google/callback
+```
+
+## Google Cloud Console Setup
+
+1. Visit [Google Cloud Console](https://console.cloud.google.com/)
+2. Create a new project or select an existing project
+3. Enable Google+ API and Google Identity API
+4. Create an OAuth 2.0 Client ID in the "Credentials" page
+5. Configure authorized redirect URIs:
+       - Development environment: `http://localhost:7130/api/auth/oauth/google/callback`
+    - Production environment: `https://yourdomain.com/api/auth/oauth/google/callback`
+
+## API Endpoints
+
+### 1. Get Google OAuth Authorization URL
+
+**Endpoint:** `GET /api/auth/v1/google-auth`
+
+**Parameters:**
+- `redirect_url`: Redirect URL after successful login
+
+**Response:**
+```json
+{
+  "success": true,
+  "data": {
+    "auth_url": "https://accounts.google.com/oauth/authorize?..."
+  }
+}
+```
+
+**Example:**
+```bash
+curl "http://localhost:7130/api/auth/v1/google-auth?redirect_url=http://localhost:7131/dashboard"
+```
+
+### 2. Google OAuth Callback Handling
+
+**Endpoint:** `GET /api/auth/oauth/google/callback`
+
+**Parameters:**
+- `code`: Authorization code returned by Google
+- `state`: State parameter (optional)
+
+**Process:**
+1. Receive Google authorization code
+2. Exchange for access token and ID token
+3. Verify ID token and retrieve user information
+4. Find or create user record
+5. Generate JWT token
+6. Redirect to specified URL with token information
+
+**Redirect URL Format:**
+```
+{redirect_url}?token={jwt_token}&user_id={user_id}&email={email}&name={name}
+```
+
+## User Flow
+
+### New User Registration
+1. User clicks "Sign in with Google"
+2. Redirect to Google authorization page
+3. After user authorization, system creates new user record:
+   - Create basic authentication record in `auth` table
+   - Create Google identity record in `identifies` table
+   - Create user profile record in `profiles` table
+4. Return JWT token and user information
+
+### Existing User Login
+1. User clicks "Sign in with Google"
+2. Redirect to Google authorization page
+3. After user authorization, system:
+   - Searches for user in `identifies` table by `provider` and `provider_id`
+   - Updates `last_login_at` timestamp
+4. Return JWT token and user information
+
+### Email Association
+- If user already exists but not associated with Google account, system will automatically associate
+- If Google account is already associated with another user, an error will be returned
+
+## Frontend Integration Example
+
+```javascript
+// 1. Get authorization URL
+const response = await fetch('/api/auth/v1/google-auth?redirect_url=/dashboard');
+const { auth_url } = await response.json();
+
+// 2. Redirect to Google authorization page
+window.location.href = auth_url;
+
+// 3. Handle returned token in callback page
+const urlParams = new URLSearchParams(window.location.search);
+const token = urlParams.get('token');
+const userId = urlParams.get('user_id');
+
+if (token) {
+  // Store token
+  localStorage.setItem('auth_token', token);
+  // Navigate to main page
+  window.location.href = '/dashboard';
+}
+```
+
+## Error Handling
+
+Common error codes:
+
+- `MISSING_FIELD`: Missing required parameters
+- `INVALID_CREDENTIALS`: Google token verification failed
+- `ALREADY_EXISTS`: User already exists
+
+## Security Considerations
+
+1. Ensure `GOOGLE_CLIENT_SECRET` environment variable is stored securely
+2. Use HTTPS in production environment
+3. Validate redirect URL legitimacy
+4. Regularly rotate JWT keys
+5. Monitor abnormal login activities
+
+## Troubleshooting
+
+1. **"Invalid redirect_uri" Error**
+   - Check redirect URI configuration in Google Cloud Console
+   - Ensure it matches the `GOOGLE_REDIRECT_URI` environment variable
+
+2. **"Invalid client" Error**
+   - Verify `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` are correct
+   - Ensure necessary APIs are enabled in Google Cloud Console project
+
+3. **"Token verification failed" Error**
+   - Check network connectivity
+   - Verify Google API service status
+   - Confirm client ID configuration is correct

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Insforge Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.