insforge 1.2.10 → 1.4.8

package/CODE_OF_CONDUCT.md

@@ -1,128 +1,128 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-tony.chang@insforge.dev.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 3.0, available at
-[https://www.contributor-covenant.org/version/3/0/code_of_conduct/](https://www.contributor-covenant.org/version/3/0/code_of_conduct/)
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+tony.chang@insforge.dev.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 3.0, available at
+[https://www.contributor-covenant.org/version/3/0/code_of_conduct/](https://www.contributor-covenant.org/version/3/0/code_of_conduct/)
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -1,126 +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 documentation
-- `/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
+# 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 documentation
+- `/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

@@ -1,30 +1,30 @@
-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 auth/package.json ./auth/
-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
-# These must be defined as ARG because Vite replaces import.meta.env.VITE_* at build time
-ARG VITE_API_BASE_URL
-ARG VITE_PUBLIC_POSTHOG_KEY
-
-# Build frontend and auth app with environment variables 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"
+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 auth/package.json ./auth/
+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
+# These must be defined as ARG because Vite replaces import.meta.env.VITE_* at build time
+ARG VITE_API_BASE_URL
+ARG VITE_PUBLIC_POSTHOG_KEY
+
+# Build frontend and auth app with environment variables 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"