What the data for this category looks like
Data sources for advertising compliance recordkeeping include advertising platform backends, customer qualification documents, contract systems, and publicly available regulatory rules. Daily processed documents include advertising review forms, qualification attachments, delivery records, and rectification notices, covering both structured fields and unstructured files. Data updates are triggered on demand per single advertising campaign or monthly cycle, with no fixed batch update schedule. Data fields include advertiser identifiers, delivery time periods, compliance qualification numbers, rectification statuses, and more. Multi-source data association storage must be supported.
What constraints these characteristics impose on deployment and upgrades
Since data updates are triggered on demand per campaign or monthly cycle, storage configurations that support on-demand writing must be supported during deployment to avoid resource waste from fixed batches. Multi-source data requires integration with different storage media, so storage parameters for both structured and unstructured data must be configured simultaneously. Data errors in compliance scenarios can lead to regulatory penalties, so storage reliability and permission isolation must be ensured during deployment. Large-volume qualification attachments and delivery record files require distributed storage configurations adapted to intranet environments to avoid single-node storage bottlenecks. The update rhythm triggered per campaign also requires cache configurations that can flexibly adapt to temporary high-concurrency write requests.
How to configure the settings
The following configurations are adapted for FastGPT v4.17.0, and meet the deployment and upgrade requirements for the advertising compliance recordkeeping scenario.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://[username]:[password]@[intranet IP]:27017/fastgpt_compliance?authSource=admin | Unstructured data such as advertising compliance recordkeeping delivery records and rectification notices is suitable for storage with MongoDB, adapting to storage requirements for multi-document structures |
PG_URL | postgresql://[username]:[password]@[intranet IP]:5432/fastgpt_compliance | Structured fields from advertising review forms and contract systems are suitable for storage with PostgreSQL, supporting complex associated queries |
REDIS_URL | redis://:[password]@[intranet IP]:6379/0 | Cache compliance qualification verification results and session information, adapting to the update rhythm triggered per campaign to reduce repeated database queries |
STORAGE_S3_ENDPOINT | http://[intranet storage IP]:9000 | Adapt to the large file storage requirements for qualification attachments and delivery records, supporting distributed file access in intranet environments |
DB_MAX_LINK | 20–30 connections | Balance concurrent connection requirements for multiple data sources, avoiding business impact from exhausted single database connections |
FE_DOMAIN | https://compliance-fastgpt.internal-domain | Configure the frontend access address, adapting to internal permission control and access paths for compliance scenarios |
Three common configuration errors
- Symptom: After deploying with docker-compose, the compliance recordkeeping module does not appear in the frontend interface. Cause:
FE_DOMAINorROOT_KEYis not configured correctly, leading to failed permission verification between the frontend and backend, and the module fails to load normally. - Symptom: During intranet deployment, the compliance recordkeeping storage service restarts continuously. Cause:
STORAGE_S3_ENDPOINTorREDIS_URLis not configured correctly, leading to failure to establish connections for storage or cache services, triggering restarts. - Symptom: After configuring a new version of the compliance verification model, old version logic is still used during calls. Cause: The cache configuration corresponding to
REDIS_URLis not updated synchronously, and old version verification result caches are not cleared, leading to reuse of historical configurations.
How to confirm the configuration is complete
- Run the
docker-compose logs -f fastgpt fastgpt-apicommand to view logs related to database connections. Noconnection refusedorauth failederrors indicates that basic connection configurations are normal. - Upload a test qualification attachment via the upload entry of the compliance recordkeeping module, confirm that the file can be stored normally and associated with the corresponding advertising campaign record.
- Simulate generating an advertising review record, check whether a corresponding entry is created in the corresponding database to verify that the data persistence function is working properly.
- Access the frontend address corresponding to
FE_DOMAIN, log in and enter the compliance recordkeeping module, confirm that all configuration items are loaded correctly, and no prompts for missing configurations are displayed.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.