What Data for This Category Looks Like
Data sources for this category include customer color swatches, formula libraries, dye chemical batch records, dye vat control systems, colorimeters, setting machines, and environmental monitoring equipment. Data updates occur per vat, per batch, or per shift. A single update covers documents including dyeing formulas, chemical weighing records, dye vat temperature curves, proofing confirmation sheets, color difference reports, setting process sheets, and sewage ledgers. Document fields include dye vat number, batch number, temperature range, color difference ΔE value, discharge concentration, and more. Corresponding units include vat runs, batches, ℃, mg/L, and more.
Constraints Imposed by These Characteristics on Deployment and Upgrade
High-frequency per-vat and per-batch data updates require configuring sufficient concurrent connection resources during deployment to avoid data write delays. Multi-source heterogeneous data sources (instrument export files, electronicized paper ledgers, structured data from formula libraries) require compatibility with import and parsing of multiple file formats during upgrades. Strong correlation between professional fields and units requires support for custom field mapping during deployment to ensure field consistency between process documents and exception reports. The characteristics of wet chemical batch processing require binding batch association relationships in storage and query logic to avoid cross-batch data confusion.
How to Set Configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://{admin_user}:{admin_pass}@{db_host}:27017/fastgpt_dyeing?authSource=admin | Stores unstructured batch process data such as dye vat curves and color difference reports, and adapts to high-frequency write requirements |
REDIS_URL | redis://:{redis_pass}@{redis_host}:6379/0 | Caches frequently accessed dyeing formulas and dye chemical batch data to reduce database query latency |
STORAGE_S3_ENDPOINT | http://{minio_host}:9000 | Stores large quantities of dye vat curve images and raw data files exported by colorimeters, and adapts to factory intranet storage requirements |
DB_MAX_LINK | 200 | Adapts to high-frequency data updates per vat and per batch, maintaining sufficient database concurrent connection count |
FE_DOMAIN | https://dyeing-fastgpt.internal-factory.com | Binds the factory intranet exclusive access domain name to ensure matching between frontend and backend interface addresses |
FILE_TOKEN_KEY | {32-bit randomly generated string} | Generates secure file access tokens to prevent unauthorized access to confidential process documents and production data |
Three Common Misconfigurations
- Symptom: A network error is prompted when deleting a self-built application. Cause: The
FE_DOMAINconfiguration does not match the factory intranet access address, causing the frontend request to fail to correctly resolve the backend interface address. - Symptom: An error "Cannot read properties of undefined" appears on the page when calling a locally deployed pdf-marker to process dye vat curve PDFs. Cause:
STORAGE_S3_ENDPOINTis not configured correctly, causing the file storage path to fail to be read properly. - Symptom: After upgrading to FastGPT v4.17.0, shared process document links can be accessed without authentication. Cause: The
FILE_TOKEN_KEYconfiguration was not updated synchronously, or the environment variable for key storage was not migrated correctly during the upgrade.
How to Verify Successful Configuration
- One can log in to the FastGPT backend, enter the database configuration page, click the test connection button, and verify the connectivity of
MONGODB_URIandREDIS_URL. - One can upload a dye vat curve PDF file to the system, check whether the file can be stored and previewed normally, and confirm that the
STORAGE_S3_ENDPOINTconfiguration takes effect. - One can create a test application, attempt to delete the application after creation, check whether the network error is no longer prompted, and confirm that the
FE_DOMAINconfiguration is correct. - One can generate a shared link for a process document, access the link using an unlogged browser, check whether authentication information is required, and confirm that the
FILE_TOKEN_KEYconfiguration takes effect.
The values provided are common starting points and should be evaluated against the user’s own samples.