What Data This Category Includes
Data for this category comes from Gerber files, drill files, and BOMs provided by customers, as well as structured data from factory CAM systems, production equipment parameters, bath test results, AOI inspection reports, electrical testing reports, and laboratory slicing reports. Data is updated in batches per production run, per shift, or via continuous collection. Daily documents include engineering production instructions, Gerber parsing records, drilling and lamination parameters, chemical solution analysis records, and various inspection reports. Data fields include layer information, aperture specifications, copper thickness parameters, defect coordinates and types, and follow standardized record formats matching production workflows.
Constraints During Deployment and Upgrade
Data sources for this category are dispersed, including external files uploaded by customers and structured data from internal factory systems. During deployment, systems must support multi-source file parsing and cross-system data integration, and corresponding storage and database connection parameters must be configured correctly. Data update frequencies vary, with updates per production run, per shift, or via continuous collection. During deployment, dual modes for batch import and streaming collection must be supported to avoid data backlog. Document types are diverse but have fixed structures, so corresponding file parsing templates must be pre-configured. During upgrades, compatibility must be maintained for new Gerber versions or inspection report formats. Data fields are tightly bound to production workflows, so field expansion space must be reserved during deployment to adapt to parameter definition differences across different factories.
Configuration Settings
These configurations are adapted for FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 10–20 concurrent connections | Adapts to the concurrent data collection requirements of multi-source PCB manufacturing data, and prevents database connection exhaustion |
MONGODB_URI | Use mongodb://localhost:27017/fastgpt_pcb for local deployments, use the corresponding cluster address for external connections | Stores unstructured documents such as AOI reports and slicing reports, matching the storage requirements of the large number of inspection files in this category |
REDIS_URL | Use redis://localhost:6379 for local deployments, use the corresponding cache cluster address for external connections | Caches frequently accessed Gerber parsing results and production parameters to reduce redundant computation overhead |
FE_DOMAIN | Factory intranet domain name or publicly bound domain name | Adapts to intranet deployment scenarios for PCB factories, ensuring front-end pages can access internal resources normally |
STORAGE_S3_ENDPOINT | Configure according to the actual address of the factory's object storage service | Stores batch-uploaded customer Gerber files and production records, supporting storage requirements for multi-source data |
ROOT_KEY | Randomly generated 32-character string | Used for system backend permission verification, ensuring access security for the deployment environment |
Three Common Configuration Errors
- Symptom: After running the container deployment command, the downloaded configuration file returns only a single line of 404 content. Cause: Correct network proxy or repository access permissions are not configured, preventing retrieval of official deployment files.
- Symptom: All containers finish starting, but the front-end page cannot be accessed, with a connection refused prompt. Cause: The
FE_DOMAINconfiguration does not match the actual deployment port or intranet domain name, or firewall rules for the corresponding port are not opened. - Symptom: When attempting to add a third-party model service, a connection refused error is reported. Cause: Port mapping for the model service is not configured correctly, or the
DB_MAX_LINKparameter is not adjusted according to the concurrency limit of the third-party model service, resulting in request blocking.
How to Verify Successful Configuration
- Run a database connection test command to verify that the
MONGODB_URIandREDIS_URLconfigurations can establish normal connections. - Access the address configured in
FE_DOMAINto confirm that the front-end page loads normally and there are no resource loading failure prompts. - Upload a test Gerber file to verify that the system can parse it normally and generate corresponding work records.
- Check the storage bucket corresponding to
STORAGE_S3_ENDPOINTto confirm that uploaded production documents can be stored and read normally.
The values given are common starting points and should be measured against the reader's own samples.