What Data for This Category Looks Like
This category’s data primarily includes documents such as dyeing formulas, chemical dosing records, dye vat operation curves, sample confirmation sheets, color difference reports, setting process sheets, and sewage ledgers. Source data also includes customer color samples, formula libraries, dye chemical batch ledgers, dye vat control data, colorimeter outputs, setting machine parameters, and environmental monitoring records. Data updates occur on a per vat, per batch, or per shift cadence. Individual records contain fields such as batch identifiers, process parameters, and test results. Some data is output directly from industrial devices, with no unified standardized format template.
Constraints on Deployment and Upgrade
This category has high-frequency data updates and dispersed data sources. Deployment must support access to multi-source heterogeneous data, including data directly from industrial devices and manually entered paper documents. During upgrades, interruptions to high-frequency updated business data links must be avoided. Existing historical datasets such as dye chemical batches and dyeing formulas must remain compatible. Data includes production and environmental protection related content. Deployment must ensure data storage and access comply with corresponding business requirements. Upgrade configuration must retain the association relationships of original data. Single batch data volume is large. Sufficient storage resources must be planned during deployment to handle long-term data accumulation.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 | This category generates data at high frequency per vat and batch. Sufficient database connections must be maintained to handle concurrent writes and queries |
PG_URL | Alibaba Cloud RDS PostgreSQL instance address:5432/fastgpt_ranzheng | Structured data for this category such as dye chemical batches and color difference reports is suitable for storage with PostgreSQL. Configure the corresponding instance when deploying via Alibaba Cloud RDS |
REDIS_URL | Local Redis instance address:6379 or Managed Redis service address | High-frequency queried data such as dyeing formulas and customer color samples must be cached to reduce database load |
STORAGE_S3_ENDPOINT | Alibaba Cloud OSS-compatible endpoint | Large files for this category such as dye vat curves and raw colorimeter data are suitable for storage with object storage. Must be compatible with Alibaba Cloud Object Storage Service |
FILE_TOKEN_KEY | 32-bit random encrypted string | Secure access tokens must be generated for uploaded documents such as process sheets and color difference reports to prevent unauthorized access |
ROOT_KEY | Encrypted administrator key | Deployment management permissions must be secured. This key is only used for initialization and advanced configuration operations |
Three Common Misconfigurations
- Symptom: A 10060 timeout error is returned when connecting to Alibaba Cloud RDS, and a database connection cannot be established. Cause: The public IP of the FastGPT deployment server was not added to the RDS instance whitelist, resulting in blocked access.
- Symptom: After upgrading to FastGPT v4.17.0, some historical configurations fail to load, and the system prompts that the configuration file is missing. Cause: Key configuration items from the legacy
config.jsonwere not migrated to the new environment variable configuration method as specified in documentation, resulting in failure to read original parameters after upgrade. - Symptom: When batch importing dye vat curve data, the system returns a field mismatch error, and some data cannot be stored in the database. Cause: The multi-source heterogeneous characteristics of this category’s data were not accommodated. A universal data import template was used directly, and dedicated fields such as dye vat temperature and time were not mapped.
How to Verify Successful Configuration
- Run the built-in database connection test tool to verify that services corresponding to
PG_URLandREDIS_URLcan read and write data normally. - Upload a dyeing formula document, then download the file using the generated access token to confirm there are no permission errors and the file is complete.
- Start a simulated high-frequency data write task, and observe that database connection pool utilization does not exceed the configured threshold.
- Access the management backend, and confirm that only accounts holding the
ROOT_KEYcan access the advanced configuration page.
The values provided are common starting points and should be evaluated against respective samples.