What the data for this category looks like
Data related to inspection and process record audit for metal cutting machining comes from product drawings and 3D models, CAPP/CAM systems, machine tool collection terminals, tool management systems, MES, and measuring and inspection equipment. Data updates are triggered by work orders, single-piece machining, spot checks, or tool changes. It covers documents including process routes, operation cards, tool lists, CNC programs, first-piece inspection records, patrol inspection forms, and measuring tool calibration records. Data fields include operation number, tool model, inspection dimensions, calibration validity period, and others. Common units include millimeters, minutes, revolutions per minute, and similar units.
What constraints these characteristics impose on deployment and upgrade
Data for this category comes from multiple scattered sources and updates frequently. It requires interfacing with multiple systems, so multiple data source connection parameters must be configured during deployment. Different types of documents vary widely in size, from text records in patrol inspection forms to tens of megabytes of CNC programs and 3D models. This requires adapting to different file storage strategies. Most workshop scenarios use intranet deployment, so public network access scope must be restricted. In addition, inspection records and process data are strongly correlated. The concurrency capability of the database connection pool must be ensured to avoid read-write conflicts.
How to configure the settings
All configuration items below are compatible with FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 10–15 | Work orders and inspection records for metal cutting machining update frequently. This connection pool size supports concurrent read-write requests from workshops |
MONGODB_URI | Intranet-accessible MongoDB instance address with database authentication parameters | Used to store unstructured process documents, 3D models and inspection records. Intranet deployment ensures data security |
REDIS_URL | Intranet Redis address on port 6379, with memory limit set to 2048 MB | Caches tool wear data and temporary patrol inspection status, reduces repeated database queries, and improves system response speed |
STORAGE_S3_ENDPOINT | Intranet object storage address for workshops, with chunked upload threshold set to 100 MB | Adapts to storage and download of large files such as CNC programs and 3D models, avoiding single-file upload timeouts |
FE_DOMAIN | Intranet access domain name for workshops, or IP port in 192.168.x.x:3000 format | For intranet deployment scenarios for workshop operators, avoids public network exposure risks |
FILE_TOKEN_KEY | Randomly generated 32-bit string | Protects the security of file download links, prevents unauthorized access to process and inspection documents |
Three common mistakes
- Phenomenon: An
Access denied for user 'fastgpt'@'localhost'error occurs after restarting the Docker container. Cause: The database mount volume permissions are reset after restart, and the access configuration of the original database user is not retained. - Phenomenon: Some historical process documents cannot be retrieved normally after cross-version upgrade. Cause: The upgrade scripts were not executed in version order, and skipped versions did not complete data structure migration and adaptation.
- Phenomenon: Only one graphics card is used after deployment on a multi-GPU server. Cause: Graphics card scheduling parameters are not configured in the startup script, and the available graphics card range is not specified.
How to confirm the configuration is complete
- Run the built-in database connection test tool in FastGPT, verify that the connection pool configured via
DB_MAX_LINKcan normally handle concurrent read-write requests. - Upload a 120 MB CNC program file, confirm that the storage service configured via
STORAGE_S3_ENDPOINTcan normally receive the file and return a valid download link. - Restart the Docker container, access the intranet address configured via
FE_DOMAIN, confirm that the system can normally load the document list such as process routes and inspection records. - Check the upgrade log, confirm that there are no data migration failure prompts during the cross-version upgrade process, and the retrieval function for historical documents works normally.
The values provided are common starting points and should be measured against the reader's own samples.