What the data for this category looks like
Data for cosmetics manufacturing process and exception reports comes from registered and filed formulas, raw material safety documents, weighing and emulsification equipment, ERP/MES systems, laboratory test records, and packaging material version archives. Data is added with every production batch and every line change. Daily documents include formula process sheets, weighing and feeding records, emulsification and filling operation records, cleaning and site clearance records, semi-finished and finished product test reports, and label review forms. Data fields include formula component proportions, operating temperature parameters, production batch numbers, and packaging material version numbers. Corresponding units include grams, degrees Celsius, and batch numbers.
What constraints do these characteristics impose on deployment and upgrade
Multi-source scattered data, high-frequency updates, and compliance requirements create multiple deployment and upgrade constraints. Configure sufficient database connection pool capacity during deployment to support simultaneous data reporting from multiple devices and systems. Ensure data migration compatibility during upgrades to avoid field mapping loss, to handle high-frequency data updates during line changes. Deploy stable cache and storage services during deployment to support real-time verification logic for formula and label data required by compliance rules. Adapt image versions for different hardware environments during upgrades to support cross-architecture deployments, such as arm64 architecture openeuler systems.
How to set configurations
The following configurations are based on FastGPT v4.17.0, and are adapted for drafting process documents and exception reports for cosmetics manufacturing:
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 | Adapts to concurrent connection requirements for simultaneous data reporting from multiple devices, including weighing, emulsification, and test equipment. Matches data submission frequency per production batch. |
PG_URL | postgresql://fastgpt:fastgpt@pg:5432/fastgpt | Stores structured process records, exception reports, and formula filing data. Uses the default PostgreSQL service port for containerized deployments. |
REDIS_URL | redis://redis:6379/0 | Caches real-time verification rules, batch session data, and routing information for model call load balancing. Supports high-frequency data processing. |
STORAGE_S3_ENDPOINT | Internal enterprise object storage service address | Stores large-volume emulsification records, test reports, and packaging material scan files. Meets long-term archiving requirements for multi-batch data. |
FE_DOMAIN | https://fastgpt.internal.cosmetic.com | Configures the access domain name for the frontend page. Ensures normal resolution of static resource loading and callback interfaces. |
ROOT_KEY | Randomly generated 32-character string | Sets the highest-privilege access key for the configuration management platform. Ensures secure management of configurations and data. |
Three common errors
- Symptom: Database connection errors appear every few hours after containerized deployment. Restoration requires deleting and redeploying the PostgreSQL container. Cause: The
DB_MAX_LINKparameter is not configured, or its value is set too low. Multi-batch production data submissions exhaust the database connection pool, and idle connections are not released in a timely manner. - Symptom: After directly upgrading from an old version to the latest version, formula component fields on process sheets cannot match filed data normally. Cause: Upgrades were not completed in version gradient. Data structure changes during cross-major-version migration were not adapted. Field mapping rules were not verified in advance.
- Symptom: When deploying on an arm64 architecture openeuler system, the frontend page cannot load static resources. Cause: The arm64-compatible image version was not used, or
FE_DOMAINwas not correctly configured as the internal access address, leading to incorrect resource path resolution.
How to confirm the configuration is complete
- Use a database management tool to check the active connection count of the connection pool. Confirm the count does not exceed the
DB_MAX_LINKconfiguration value. - Upload a real cosmetics formula process sheet to trigger the exception report generation process. Verify model call channel allocation matches preset load balancing rules.
- Run container status check commands in the deployment environment. Confirm all service containers are running, with no failed startup or abnormally exited logs.
- Access the configured
FE_DOMAINaddress. Confirm the frontend page loads normally, and process documents can be submitted for verification.
The values provided here are common starting points. They should be evaluated against the reader's own samples.