What This Category’s Data Looks Like
Collect coal mining production business process data from internal coal mine scheduling management systems, safety supervision systems, license application systems, logistics service systems, and similar internal tools. Synchronize data updates each time a process is submitted, approved, or completed. Updates trigger at business process nodes. Use this document structure: include these fields: unique process identifier, node name, responsible person’s position, required document type, processing time limit, approval status. Divide document types into electronic and physical copies. Measure processing time limits in hours or days. Store data across multiple internal databases. Require internal network dedicated lines for connections. Do not provide a unified publicly accessible interface.
Constraints on Deployment and Upgrade
Distribute coal mining business process data across multiple internal network databases. Configure connection parameters for multiple data sources during deployment. Adapt deployments to internal network environments without public network access. Adjust data update frequency based on business processing volume. Generate dense read and write requests during peak operating periods. Adjust database connection pool parameters to maintain stability. Connect internal object storage services to store electronic process documents. Configure dedicated storage endpoint parameters. Update access permission configurations for data sources synchronously during upgrades. Prevent process data reading failures caused by permission changes.
How to Set Configuration Values
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PG_URL | postgresql://coal_admin:secure_pass@internal-db:5432/coal_business?sslmode=disable | Connects to the PostgreSQL database for internal coal mine business processes, disables SSL to adapt to internal network environments |
MONGODB_URI | mongodb://internal-mongo:27017/coal_flow_db | MongoDB instance storing process node logs and approval records, adapted for internal network deployment |
DB_MAX_LINK | 20–30 | Meets high-frequency read/write requirements of business processes, prevents connection exhaustion |
STORAGE_S3_ENDPOINT | http://internal-storage:9000 | Connects to the internal coal mine object storage service for storing electronic processing documents |
FE_DOMAIN | https://coal-proc.internal | Configures the internal network access frontend domain, adapted for coal mine internal network access scenarios |
REDIS_URL | redis://internal-redis:6379/0 | Caches process node and user session data, improves access response speed |
Three Common Misconfigurations
- Upload files or images and receive errors. Errors persist after redeployment. Cause: Fail to configure
STORAGE_S3_ENDPOINTto the internal coal mine storage address. Public network storage cannot be accessed in internal network environments. - Run local development deployments and encounter database installation steps that redirect to the Docker Compose deployment process. Cause: Fail to correctly configure local database connection parameters. The installation script automatically falls back to containerized deployment solutions.
- Use public cloud versions and experience connection timeout errors. Cause: Fail to configure
FE_DOMAINto the official domain bound to the public cloud. This causes a mismatch between frontend and backend service addresses, preventing normal request routing.
How to Confirm Configuration Is Complete
- Access the configured
FE_DOMAINaddress. Verify the frontend page loads normally, with no domain resolution or connection timeout errors. - Run the built-in database connection test tool. Confirm data sources configured via
PG_URLandMONGODB_URIcan establish normal connections and read test data. - Upload a test electronic document file. Confirm the file can be stored normally in the storage service corresponding to the configured
STORAGE_S3_ENDPOINT, with no upload failure prompts. - Check Redis service logs. Confirm the cache service configured via
REDIS_URLhas established normal connections, with no authentication or connection errors.
The values provided are common starting points and should be evaluated against the reader’s own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.