What data for this category looks like
Data for this category typically comes from customer product models, mold flow or forming simulation files, CAD/CAM source files, machining and measurement records, and test sample inspection data. Daily generated documents include mold design task sheets, DFM reports, part engineering drawings, machining process cards, mold trial reports, mold modification notices, and mold history logs. Data updates are managed per individual project, synchronized after each mold trial or modification. Documents include clear fields such as part dimensions, mold structure parameters, machining tolerances, and mold trial defect records. No unified fixed units are used, adjusted based on project requirements.
What constraints these characteristics impose on deployment and upgrade
The multi-source heterogeneous engineering files and high-frequency project-based updates of this category create specific constraints for the deployment and upgrade phase. First, storage and parsing of non-standard format files such as CAD and mold flow simulation files must be supported, so appropriate storage service parameters must be configured during deployment. Second, the data volume of a single project grows with mold trial and modification iterations, so database connection parameters must be properly configured to ensure read and write performance. Additionally, cross-supplier collaborative audit needs require configuration of permission management parameters during deployment to prevent unauthorized access to project documents. The upgrade phase must ensure full migration of core data such as historical mold history logs and mold trial reports to avoid project data loss.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://user:pass@host:27017/fastgpt?authSource=admin | Stores structured data such as mold project trial reports and modification records. A dedicated database instance must be specified to ensure data isolation |
REDIS_URL | redis://:pass@host:6379/0 | Caches frequently accessed mold part drawings and DFM report preview data to reduce database read and write pressure. Calibrated based on actual measurements |
STORAGE_S3_ENDPOINT | http://minio.host:9000 | Stores large-volume engineering files such as CAD source files and mold flow simulation files. Must match the address of the self-built object storage service |
DB_MAX_LINK | 50–80 | When multiple team members collaborate on audit for a single project, the number of database connections must cover concurrent access requirements to avoid connection exhaustion |
FE_DOMAIN | https://audit.mold-manufacture.com | Configures the frontend access domain name to ensure team members access the audit process through the specified address and avoid cross-domain issues |
ROOT_KEY | Custom high-strength random string | Manages the highest platform permissions, used to configure audit permissions for team members and project access scopes |
Three common mistakes
- Symptom: After deployment using docker-compose, all model calls return errors. Container logs show database connection timeouts. Cause: The
DB_MAX_LINKparameter was not adjusted based on the concurrent access requirements of mold projects, leading to database connection pool exhaustion and inability to process audit process requests. - Symptom: After upgrading to FastGPT v4.17.0, the existing supplier audit sample workflow fails to run normally, prompting missing workflow nodes. Cause: The relational database structure pointed to by
PG_URLwas not updated synchronously during the upgrade, so the audit record table relied on by the sample workflow was not migrated completely. - Symptom: Team members cannot create independent mold audit projects, prompting no permission to access the deployed program. Cause: The permission token generated using
ROOT_KEYwas not configured correctly, and access scopes for collaborative members were not assigned to corresponding projects, leading to permission verification failure.
How to confirm configuration is correct
- Access the configured
FE_DOMAINaddress, confirm that the frontend page loads normally with no cross-domain or access errors. - Upload a mold part drawing file, confirm that it can be stored normally and a preview is generated, verifying that the
STORAGE_S3_ENDPOINTconfiguration takes effect. - Initiate a supplier audit workflow, submit mold trial report data, confirm that the database can write and retrieve data normally, verifying that the
MONGODB_URIandDB_MAX_LINKconfigurations meet concurrent access requirements. - Use the permission token generated with
ROOT_KEYto invite test members to access the project, confirm that the permission verification logic works normally.
The values provided are common starting points and should be measured against the reader's own samples.