What the Data for This Category Looks Like
This category covers data from skincare, haircare, makeup, and special cosmetics manufacturing enterprises. Core documents include formula process sheets, weighing and feeding records, emulsification and filling records, cleaning and site clearance records, semi-finished and finished product inspection reports, and label review documents. Data is sourced from registered and filed formulas, raw material safety materials, production equipment logs, ERP/MES systems, laboratory test data, and packaging material version records. Updates occur with each production batch or each line change. Each document includes fields such as formula ingredients, feeding quantities, production parameters, inspection indicators, batch numbers, and packaging material information. Units are adjusted according to the requirements of the corresponding production link documents.
Constraints on Deployment and Upgrade
This deployment was adapted for FastGPT v4.17.0. Since data updates are tied to production batches and line changes, deployment must support document synchronization by batch to avoid mixing data across batches. Multi-source data comes from different systems such as equipment, ERP, and laboratories. Deployment must support multi-format access, and configure corresponding permissions to isolate data across departments. The frequency of single line changes or batch updates is high. Upgrades must ensure the data synchronization link is not interrupted, to avoid data loss in production links. Formulas and labels are subject to filing requirements. Deployment must retain the original data traceability path to ensure traceability back to filed information. It must also restrict unauthorized modification of production-related document fields.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | Configure as the connection string for an independent cluster, reserve 30% extra connections | Cosmetics production data is stored by batch, and data volume fluctuates greatly between batches. Reserved connections prevent connection exhaustion during concurrent synchronization |
REDIS_URL | Set to cluster mode, with a key expiration time of 86400 seconds | Temporary caching of batch data needs to be cleaned according to production cycles. The expiration time matches the processing cycle for single-day production batches |
STORAGE_S3_ENDPOINT | Configure as the endpoint address of the enterprise's internal object storage service | Production documents require local storage to ensure compliance. Internal endpoints avoid external network latency affecting bulk file uploads |
DB_MAX_LINK | Set to 150–200 | Matches the concurrent data synchronization request volume from multiple devices, ERP, and laboratories, preventing database connection pool overflow |
FE_DOMAIN | Configure as the domain name of the enterprise's internal production management system | Ensures the traceability page can integrate seamlessly with existing production systems, facilitating access for production personnel |
Three Common Misconfigurations
- When adding a model during local deployment, the test returns
403 status code (no body). The cause is that theROOT_KEYpermission verification parameter was not configured correctly, leading to interface requests failing identity verification. - After calling the file upload API, the status of file data and indexing cannot be confirmed. The cause is that no corresponding callback or polling mechanism was configured, and the status synchronization logic after file upload was not bound.
- After upgrading, the upgrade entry in the document interface cannot be found. The cause is that the background configuration item path for the upgraded version has changed, and internal operation guidelines were not updated synchronously.
How to Verify a Complete Configuration
- Attempt to synchronize a batch of recent production batch documents. Check whether the corresponding batch data collection is generated in the database corresponding to
MONGODB_URI, with no connection errors. - Access the domain name configured for
FE_DOMAIN. Confirm that the traceability page loads normally and that associated interfaces of the internal production system can be called. - Upload a test formula process sheet. Check whether the storage service corresponding to
STORAGE_S3_ENDPOINTsuccessfully receives the file, with no upload failure logs. - After configuring the key expiration time for
REDIS_URL, wait for the corresponding duration. Check whether cached keys are automatically cleaned, with no residual invalid data.
The values provided are common starting points and should be measured against the reader's own samples.