This chapter mainly introduces the configuration file content of the FinClip Digital Management Platform.
In FinClip private deployment, business system-related configurations are provided to the quark service through mounting for reading and management, while other services uniformly obtain them from the configuration center. In docker compose deployment environments, we use file mounting to mount configuration files. In Kubernetes or container platform environments, we use ConfigMap to mount to containers.
Configuration Description
FinClip configuration is mainly divided into two parts:
- common field, used to configure infrastructure service-related content
- services field, used to configure settings for each service
common Configuration
Database-related configuration, fill in MySQL connection and authentication information
yamlDB_MODE: mysql MYSQL_URL: user_name:password@tcp(mysql_host:3306)/db_name?charset=utf8mb4 driverName: mysql dataSourceName: user_name:password@tcp(mysql:3306)/ dbName: db_nameRedis configuration, supports single and cluster modes
yamlREDIS_MODE: single REDIS_ADDR: redis:6379 REDIS_PASSWORD: redis_passObject storage configuration, used to store static files, supports minio, tencent_cos, ali_oss, aws_s3, disk.
yamlSTORAGE_MODE: minio STORAGE_ENDPOINT: minio:9000 STORAGE_ACCESS_KEY: access_key STORAGE_SECRET_KEY: secret_key STORAGE_BUCKET_NAME: bucket_name STORAGE_S3_USE_SSL: falseBusiness-related general configuration, including default ports for services, log mode, etc.
yamlENV: fc-private EDITION: private LOG_MODE: warn HTTP_PORT: '8080' ...
services Configuration
services is an array-type field that contains related configurations for each service. Most of the time no changes are needed, but the License configuration requires attention. After you purchase and deploy FinClip, you need to update the License configuration, which is set in the finclip-cloud-license-manager service:
- SERVER_NAME: finclip-cloud-license-manager
LICENSE_ENCRYPTION_STR: License_file_content