@libredb/studio 0.9.7 → 0.9.12

package/charts/libredb-studio/values.yaml

@@ -1,286 +0,0 @@
-# -- Number of replicas. Note: SQLite storage mode only supports 1 replica.
-replicaCount: 1
-
-image:
-  # -- Container image repository
-  repository: ghcr.io/libredb/libredb-studio
-  # -- Image pull policy
-  pullPolicy: IfNotPresent
-  # -- Overrides the image tag (default: Chart appVersion)
-  tag: ""
-
-# -- Image pull secrets for private registries
-imagePullSecrets: []
-# -- Override the chart name
-nameOverride: ""
-# -- Override the full release name
-fullnameOverride: ""
-
-# =============================================================================
-# Secrets — sensitive values stored in a Kubernetes Secret
-# =============================================================================
-secrets:
-  # -- Use an existing Secret instead of creating one.
-  # When set, all other secret values are ignored.
-  existingSecret: ""
-  # -- Key name mapping for existing secrets.
-  # Override if your existing secret uses different key names.
-  existingSecretKeys:
-    jwtSecret: jwt-secret
-    adminEmail: admin-email
-    adminPassword: admin-password
-    userEmail: user-email
-    userPassword: user-password
-    llmApiKey: llm-api-key
-    oidcClientId: oidc-client-id
-    oidcClientSecret: oidc-client-secret
-    storagePostgresUrl: storage-postgres-url
-  # -- JWT signing secret (min 32 chars). Required.
-  jwtSecret: ""
-  # -- Admin account email
-  adminEmail: "admin@libredb.org"
-  # -- Admin account password. Required.
-  adminPassword: ""
-  # -- Regular user account email
-  userEmail: "user@libredb.org"
-  # -- Regular user account password. Required.
-  userPassword: ""
-  # -- LLM API key (optional, for AI features)
-  llmApiKey: ""
-  # -- OIDC client ID (required when authProvider=oidc)
-  oidcClientId: ""
-  # -- OIDC client secret (required when authProvider=oidc)
-  oidcClientSecret: ""
-  # -- PostgreSQL connection URL for storage (required when storageProvider=postgres and postgresql.enabled=false)
-  storagePostgresUrl: ""
-
-# =============================================================================
-# Config — non-sensitive values stored in a ConfigMap
-# =============================================================================
-
-# -- Authentication provider: "local" or "oidc"
-authProvider: "local"
-
-config:
-  # -- Log level
-  logLevel: "info"
-  # -- Storage provider: "local" (browser), "sqlite" (file), or "postgres" (database)
-  storageProvider: "local"
-  # -- SQLite database file path (when storageProvider=sqlite)
-  storageSqlitePath: "/app/data/libredb-storage.db"
-  # -- LLM provider: gemini, openai, ollama, custom (optional)
-  llmProvider: ""
-  # -- LLM model name (optional)
-  llmModel: ""
-  # -- LLM API URL for ollama/custom providers (optional)
-  llmApiUrl: ""
-  # -- OIDC issuer URL (required when authProvider=oidc)
-  oidcIssuer: ""
-  # -- OIDC scopes (space-separated)
-  oidcScope: "openid profile email"
-  # -- OIDC claim path for role extraction
-  oidcRoleClaim: ""
-  # -- OIDC admin role values (comma-separated)
-  oidcAdminRoles: "admin"
-
-# =============================================================================
-# Persistence — PVC for SQLite storage mode
-# =============================================================================
-persistence:
-  # -- Enable persistent storage. Auto-enabled when storageProvider=sqlite.
-  enabled: false
-  # -- Storage class name (leave empty for default)
-  storageClassName: ""
-  # -- Access modes
-  accessModes:
-    - ReadWriteOnce
-  # -- Storage size
-  size: 1Gi
-  # -- Use an existing PVC instead of creating one
-  existingClaim: ""
-  # -- Annotations for the PVC
-  annotations: {}
-
-# =============================================================================
-# Security
-# =============================================================================
-serviceAccount:
-  # -- Create a ServiceAccount
-  create: true
-  # -- Annotations (e.g., for IRSA or Workload Identity)
-  annotations: {}
-  # -- ServiceAccount name (auto-generated if empty)
-  name: ""
-  # -- Automount API credentials
-  automountServiceAccountToken: false
-
-podSecurityContext:
-  runAsNonRoot: true
-  runAsUser: 1001
-  runAsGroup: 1001
-  fsGroup: 1001
-  seccompProfile:
-    type: RuntimeDefault
-
-securityContext:
-  allowPrivilegeEscalation: false
-  readOnlyRootFilesystem: true
-  capabilities:
-    drop:
-      - ALL
-
-# -- Pod annotations
-podAnnotations: {}
-# -- Pod labels
-podLabels: {}
-
-# =============================================================================
-# Probes — uses /api/db/health endpoint
-# =============================================================================
-startupProbe:
-  httpGet:
-    path: /api/db/health
-    port: http
-  failureThreshold: 30
-  periodSeconds: 2
-
-readinessProbe:
-  httpGet:
-    path: /api/db/health
-    port: http
-  initialDelaySeconds: 5
-  periodSeconds: 10
-
-livenessProbe:
-  httpGet:
-    path: /api/db/health
-    port: http
-  initialDelaySeconds: 30
-  periodSeconds: 30
-
-# =============================================================================
-# Resources
-# =============================================================================
-resources:
-  requests:
-    cpu: 100m
-    memory: 256Mi
-  limits:
-    memory: 512Mi
-
-# =============================================================================
-# Networking
-# =============================================================================
-service:
-  # -- Service type: ClusterIP, NodePort, or LoadBalancer
-  type: ClusterIP
-  # -- Service port
-  port: 80
-  # -- Container target port
-  targetPort: 3000
-  # -- NodePort (only when type=NodePort)
-  nodePort: ""
-  # -- Service annotations
-  annotations: {}
-
-ingress:
-  # -- Enable Ingress
-  enabled: false
-  # -- Ingress class name (e.g., nginx, traefik)
-  className: ""
-  # -- Ingress annotations
-  annotations: {}
-  # -- Ingress hosts
-  hosts:
-    - host: libredb.local
-      paths:
-        - path: /
-          pathType: Prefix
-  # -- TLS configuration
-  tls: []
-  #  - secretName: libredb-tls
-  #    hosts:
-  #      - libredb.local
-
-networkPolicy:
-  # -- Enable NetworkPolicy
-  enabled: false
-  # -- Additional ingress rules
-  additionalIngress: []
-  # -- Additional egress rules
-  additionalEgress: []
-
-# =============================================================================
-# Autoscaling & HA
-# =============================================================================
-autoscaling:
-  # -- Enable HorizontalPodAutoscaler
-  enabled: false
-  # -- Minimum replicas
-  minReplicas: 2
-  # -- Maximum replicas
-  maxReplicas: 10
-  # -- Target CPU utilization percentage
-  targetCPUUtilizationPercentage: 75
-  # -- Target memory utilization percentage
-  targetMemoryUtilizationPercentage: 80
-
-podDisruptionBudget:
-  # -- Enable PodDisruptionBudget
-  enabled: false
-  # -- Minimum available pods (mutually exclusive with maxUnavailable)
-  minAvailable: 1
-  # -- Maximum unavailable pods
-  # maxUnavailable: 1
-
-# =============================================================================
-# PostgreSQL Subchart (Bitnami)
-# =============================================================================
-postgresql:
-  # -- Deploy a PostgreSQL instance for storage backend
-  enabled: false
-  auth:
-    # -- PostgreSQL username
-    username: "libredb"
-    # -- PostgreSQL password
-    password: ""
-    # -- PostgreSQL database name
-    database: "libredb_storage"
-
-# =============================================================================
-# Scheduling
-# =============================================================================
-# -- Node selector
-nodeSelector: {}
-# -- Tolerations
-tolerations: []
-# -- Affinity rules
-affinity: {}
-# -- Topology spread constraints
-topologySpreadConstraints: []
-
-# =============================================================================
-# Extra configuration
-# =============================================================================
-# -- Additional environment variables
-extraEnv: []
-#  - name: MY_VAR
-#    value: "my-value"
-
-# -- Additional envFrom references
-extraEnvFrom: []
-#  - configMapRef:
-#      name: my-config
-
-# -- Seed connections: pre-configured database connections
-seedConnections:
-  # -- Enable seed connections feature
-  enabled: false
-  # -- Inline config (rendered as YAML in ConfigMap)
-  config: {}
-  # -- Use an existing ConfigMap instead of inline config
-  existingConfigMap: ""
-  # -- Key within the ConfigMap containing the YAML config
-  configMapKey: "seed-connections.yaml"
-  # -- Cache TTL in milliseconds for config reloading
-  cacheTTL: 60000

package/components.json

@@ -1,22 +0,0 @@
-{
-  "$schema": "https://ui.shadcn.com/schema.json",
-  "style": "new-york",
-  "rsc": true,
-  "tsx": true,
-  "tailwind": {
-    "config": "",
-    "css": "src/app/globals.css",
-    "baseColor": "neutral",
-    "cssVariables": true,
-    "prefix": ""
-  },
-  "iconLibrary": "lucide",
-  "aliases": {
-    "components": "@/components",
-    "utils": "@/lib/utils",
-    "ui": "@/components/ui",
-    "lib": "@/lib",
-    "hooks": "@/hooks"
-  },
-  "registries": {}
-}

package/conductor/code_styleguides/typescript.md

@@ -1,43 +0,0 @@
-# Google TypeScript Style Guide Summary
-
-This document summarizes key rules and best practices from the Google TypeScript Style Guide, which is enforced by the `gts` tool.
-
-## 1. Language Features
-- **Variable Declarations:** Always use `const` or `let`. **`var` is forbidden.** Use `const` by default.
-- **Modules:** Use ES6 modules (`import`/`export`). **Do not use `namespace`.**
-- **Exports:** Use named exports (`export {MyClass};`). **Do not use default exports.**
-- **Classes:**
-  - **Do not use `#private` fields.** Use TypeScript's `private` visibility modifier.
-  - Mark properties never reassigned outside the constructor with `readonly`.
-  - **Never use the `public` modifier** (it's the default). Restrict visibility with `private` or `protected` where possible.
-- **Functions:** Prefer function declarations for named functions. Use arrow functions for anonymous functions/callbacks.
-- **String Literals:** Use single quotes (`'`). Use template literals (`` ` ``) for interpolation and multi-line strings.
-- **Equality Checks:** Always use triple equals (`===`) and not equals (`!==`).
-- **Type Assertions:** **Avoid type assertions (`x as SomeType`) and non-nullability assertions (`y!`)**. If you must use them, provide a clear justification.
-
-## 2. Disallowed Features
-- **`any` Type:** **Avoid `any`**. Prefer `unknown` or a more specific type.
-- **Wrapper Objects:** Do not instantiate `String`, `Boolean`, or `Number` wrapper classes.
-- **Automatic Semicolon Insertion (ASI):** Do not rely on it. **Explicitly end all statements with a semicolon.**
-- **`const enum`:** Do not use `const enum`. Use plain `enum` instead.
-- **`eval()` and `Function(...string)`:** Forbidden.
-
-## 3. Naming
-- **`UpperCamelCase`:** For classes, interfaces, types, enums, and decorators.
-- **`lowerCamelCase`:** For variables, parameters, functions, methods, and properties.
-- **`CONSTANT_CASE`:** For global constant values, including enum values.
-- **`_` Prefix/Suffix:** **Do not use `_` as a prefix or suffix** for identifiers, including for private properties.
-
-## 4. Type System
-- **Type Inference:** Rely on type inference for simple, obvious types. Be explicit for complex types.
-- **`undefined` and `null`:** Both are supported. Be consistent within your project.
-- **Optional vs. `|undefined`:** Prefer optional parameters and fields (`?`) over adding `|undefined` to the type.
-- **`Array<T>` Type:** Use `T[]` for simple types. Use `Array<T>` for more complex union types (e.g., `Array<string | number>`).
-- **`{}` Type:** **Do not use `{}`**. Prefer `unknown`, `Record<string, unknown>`, or `object`.
-
-## 5. Comments and Documentation
-- **JSDoc:** Use `/** JSDoc */` for documentation, `//` for implementation comments.
-- **Redundancy:** **Do not declare types in `@param` or `@return` blocks** (e.g., `/** @param {string} user */`). This is redundant in TypeScript.
-- **Add Information:** Comments must add information, not just restate the code.
-
-*Source: [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html)*

package/conductor/product-guidelines.md

@@ -1,43 +0,0 @@
-# Product Guidelines
-
-This document outlines the core principles that guide the development and identity of LibreDB Studio.
-
-## Tone of Voice
-
-Our communication style should reflect our position as a modern, reliable, and user-centric tool. The following hierarchy should be used when crafting any user-facing text:
-
-1.  **Innovative & Cutting-Edge:** We are a forward-thinking platform. Our language should be energetic and inspiring, highlighting advanced features and AI capabilities.
-2.  **Professional & Authoritative:** We are a serious tool for professionals. Our tone should be clear, precise, and instill confidence in our reliability and expertise.
-3.  **Friendly & Approachable:** We are here to help. Our communication should be welcoming, easy to understand, and supportive, especially during onboarding and for community interactions.
-
-## Visual Design & User Experience
-
-Our design philosophy is **Data-First & Utilitarian**. The interface must be optimized for power users who need to access and manipulate large amounts of information efficiently.
-
--   **Information Density:** Prioritize a dense, information-rich interface.
--   **Function over Form:** Practicality and speed take precedence over purely aesthetic choices.
--   **Clarity and Readability:** Despite the density, typography, and layout must ensure that data is easy to read and interpret.
-
-## Brand Messaging
-
-Our brand messaging is centered around being **Open-Source & Community Driven**.
-
--   **Transparency:** We are open about our development process, roadmap, and challenges.
--   **Extensibility:** We encourage and support community contributions, from plugins to core features.
--   **Collaboration:** We foster a strong community where users can share knowledge, best practices, and solutions.
-
-## Documentation & Learning Resources
-
-Our documentation is focused on providing **Comprehensive Technical References**.
-
--   **Accuracy and Detail:** Documentation must be precise, thorough, and technically accurate.
--   **Target Audience:** The primary audience is developers and DBAs who require deep technical knowledge.
--   **Completeness:** We aim to provide exhaustive API documentation, schema explanations, and advanced configuration guides.
-
-## New Feature Development
-
-The guiding principle for new feature development is **Innovation & Experimentation**.
-
--   **Rapid Prototyping:** We encourage the quick development and release of novel features.
--   **Embrace Experimentation:** We are not afraid to introduce experimental features to push the boundaries of what a SQL IDE can do.
--   **Fail Fast:** We learn from our experiments, iterating quickly based on user feedback and technical feasibility.

package/conductor/product.md

@@ -1,3 +0,0 @@
-# Initial Concept
-
-LibreDB Studio is a lightweight, high-performance, and secure web-based SQL editor designed to bridge the gap between heavy desktop applications and minimal CLI tools, empowering engineering teams to manage databases anywhere.

package/conductor/setup_state.json

@@ -1 +0,0 @@
-{"last_successful_step": "3.3_initial_track_generated"}

package/conductor/tech-stack.md

@@ -1,39 +0,0 @@
-# Technology Stack
-
-This document outlines the core technologies and frameworks utilized in LibreDB Studio.
-
-## Frontend
-
-*   **Framework:** Next.js 15 (App Router)
-*   **Library:** React 19
-*   **UI Frameworks:** Tailwind CSS 4, Radix UI, shadcn/ui
-*   **Editor Component:** Monaco Editor (VS Code Engine)
-*   **State/Data Grid Management:** TanStack Table & Virtual
-*   **Programming Language:** TypeScript
-
-## Backend
-
-*   **Framework:** Next.js (API Routes)
-*   **Programming Language:** TypeScript
-*   **AI Integration:** Multi-Model (Gemini, OpenAI, Ollama, Custom)
-
-## Supported Databases
-
-LibreDB Studio is designed to support a variety of relational and non-relational databases:
-
-*   PostgreSQL
-*   MySQL
-*   SQLite
-*   MongoDB
-
-## Deployment & Infrastructure
-
-*   **Containerization:** Docker
-*   **Orchestration:** Kubernetes (compatible)
-
-## Other Tools & Libraries
-
-*   **Package Manager:** Bun (recommended)
-*   **Linting:** ESLint
-*   **Styling:** PostCSS
-*   **Type Checking:** TypeScript

package/conductor/tracks/enhance_postgres_monitoring_20251227/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "enhance_postgres_monitoring_20251227",
-  "type": "feature",
-  "status": "new",
-  "created_at": "2025-12-27T12:00:00Z",
-  "updated_at": "2025-12-27T12:00:00Z",
-  "description": "Enhance existing database provider for PostgreSQL to support advanced monitoring features."
-}

package/conductor/tracks/enhance_postgres_monitoring_20251227/plan.md

@@ -1,44 +0,0 @@
-# Plan: Enhance PostgreSQL Monitoring
-
-**Track:** Enhance existing database provider for PostgreSQL to support advanced monitoring features.
-
-This plan outlines the steps to enhance the PostgreSQL provider with advanced monitoring capabilities.
-
----
-
-## Phase 1: Foundational Metrics - `pg_stat_activity` and `pg_stat_statements`
-
-### Tasks
-
--   [~] **Task:** Write tests for `pg_stat_activity` data retrieval.
--   [ ] **Task:** Implement `pg_stat_activity` data retrieval in the PostgreSQL provider.
--   [ ] **Task:** Write tests for `pg_stat_statements` data retrieval.
--   [ ] **Task:** Implement `pg_stat_statements` data retrieval in the PostgreSQL provider.
--   [ ] **Task:** Create a new API endpoint `/api/db/monitoring/postgres/activity` to expose `pg_stat_activity` data.
--   [ ] **Task:** Create a new API endpoint `/api/db/monitoring/postgres/statements` to expose `pg_stat_statements` data.
--   [ ] **Task:** Conductor - User Manual Verification 'Phase 1: Foundational Metrics' (Protocol in workflow.md)
-
----
-
-## Phase 2: Index and Table Analysis
-
-### Tasks
-
--   [ ] **Task:** Write tests for index usage statistics retrieval.
--   [ ] **Task:** Implement index usage statistics retrieval from `pg_stat_user_indexes` and `pg_stat_user_tables`.
--   [ ] **Task:** Write tests for table and index bloat estimation.
--   [ ] **Task:** Implement table and index bloat estimation queries.
--   [ ] **Task:** Create a new API endpoint `/api/db/monitoring/postgres/indexes` to expose index usage and bloat data.
--   [ ] **Task:** Conductor - User Manual Verification 'Phase 2: Index and Table Analysis' (Protocol in workflow.md)
-
----
-
-## Phase 3: Cache Performance and Finalization
-
-### Tasks
-
--   [ ] **Task:** Write tests for cache hit rate calculation.
--   [ ] **Task:** Implement cache hit rate calculation for tables and indexes.
--   [ ] **Task:** Create a new API endpoint `/api/db/monitoring/postgres/cache` to expose cache hit rate data.
--   [ ] **Task:** Refactor the monitoring provider to ensure all new functions are cohesive and well-documented.
--   [ ] **Task:** Conductor - User Manual Verification 'Phase 3: Cache Performance and Finalization' (Protocol in workflow.md)

package/conductor/tracks/enhance_postgres_monitoring_20251227/spec.md

@@ -1,31 +0,0 @@
-# Specification for Advanced PostgreSQL Monitoring
-
-**Track:** Enhance existing database provider for PostgreSQL to support advanced monitoring features.
-
-## 1. Overview
-
-This document outlines the technical specifications for enhancing the existing PostgreSQL database provider to support advanced monitoring capabilities. The primary goal is to expose key performance and health metrics from a connected PostgreSQL instance directly within the LibreDB Studio interface.
-
-## 2. Functional Requirements
-
--   **FR1: Expose `pg_stat_statements` Data:** The provider must be able to query the `pg_stat_statements` view (if the extension is enabled on the target database) and return a structured representation of the data.
--   **FR2: Expose `pg_stat_activity` Data:** The provider must query the `pg_stat_activity` view to provide real-time information about active connections, their states, and the queries they are executing.
--   **FR3: Expose Index Usage Statistics:** The provider must query `pg_stat_user_indexes` and `pg_stat_user_tables` to provide insights into index usage, including the number of index scans vs. sequential scans.
--   **FR4: Expose Table & Index Bloat:** The provider should include queries to estimate table and index bloat.
--   **FR5: Expose Cache Hit Rate:** The provider must calculate and expose the cache hit rate for indexes and tables.
-
-## 3. Non-Functional Requirements
-
--   **NFR1: Performance:** All monitoring queries must be designed to have minimal performance impact on the target database. They should be efficient and not lock resources.
--   **NFR2: Error Handling:** The provider must gracefully handle cases where the required extensions (`pg_stat_statements`) are not enabled or the user lacks the necessary permissions to view the statistics tables. It should return a clear message to the user in such cases.
--   **NFR3: Security:** The queries should be read-only and not expose any sensitive data.
--   **NFR4: Data Structure:** The data returned by the provider should be in a well-defined, easily consumable JSON format for the frontend.
-
-## 4. API Endpoint Integration
-
-The new monitoring functionalities will be exposed through a new API endpoint, likely under `/api/db/monitoring/postgres`. This endpoint will accept the connection details and return the collected monitoring data.
-
-## 5. Out of Scope
-
--   This track does not include the implementation of the frontend components to visualize the monitoring data. It is solely focused on the backend provider and API enhancements.
--   This track will not include any write operations or any actions that modify the database state.

package/conductor/tracks.md

@@ -1,8 +0,0 @@
-# Project Tracks
-
-This file tracks all major tracks for the project. Each track has its own detailed plan in its respective folder.
-
----
-
-## [~] Track: Enhance existing database provider for PostgreSQL to support advanced monitoring features.
-*Link: [./conductor/tracks/enhance_postgres_monitoring_20251227/](./conductor/tracks/enhance_postgres_monitoring_20251227/)*