Forgex 项目数据源说明

Manage Forgex multi-datasource configurations across admin, common, workflow, history, and scada databases.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/codernai14-source/Forgex --skill forgex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forgex 项目数据源说明
Source: https://github.com/codernai14-source/Forgex/tree/main/.cursor/skills/data-source-description
Command: npx skills add https://github.com/codernai14-source/Forgex --skill forgex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seamless management and isolation of Forgex's multi-datasource architecture across admin, common, workflow, history, and scada databases, enabling safe routing and configuration.

Core Features & Use Cases

  • Dynamic data source routing and isolation across multiple logical databases.
  • Unified configuration via YAML/Nacos with per-source settings and fallbacks.
  • Use cases include multi-tenant environments, cross-database reporting, and environment-specific data access.

Quick Start

Configure and switch the active data source in your service to point to forgex_admin or other sources as needed.

Frequently Asked Questions about Forgex 项目数据源说明

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multi-datasource routing and isolation in a microservice environment?▼

Multi-datasource routing and isolation is managed by centralizing configurations across admin, common, workflow, history, and scada databases. This enables safe routing and per-source naming within a microservice environment.

Can I configure dynamic data source switching using Nacos or YAML?▼

Yes, dynamic data source switching is supported via Nacos and YAML. Unified configuration provides per-source settings and fallbacks to handle runtime switching across multiple logical databases.

Does this approach support multi-tenant environments and cross-database reporting?▼

Yes, multi-tenant environments and cross-database reporting are supported use cases. The architecture provides environment-specific data access and isolation across admin, common, workflow, history, and scada databases.

What is the best way to safely access and route data across multiple logical databases?▼

Safely accessing multiple logical databases requires dynamic routing with clear guidance on usage and safe data access patterns. Configuring your service to point to specific sources like forgex_admin ensures safe isolation.

How do I switch the active data source in my backend service to point to forgex_admin?▼

To switch the active data source, configure your backend service to point to forgex_admin or other sources as needed. Runtime switching is handled dynamically via YAML or Nacos configurations.