[Feature Request]: Please adhere to the best practices of Continuous Integration (CI) for project configuration.

[shaoyie]

Is there an existing issue for the same feature request?

• I have checked the existing issues.

Is your feature request related to a problem?

No response

Describe the feature you'd like

How can there be two places, .env and service_conf.yaml, where the same parameters need to be configured, manually synchronized? This is both foolish and prone to errors. Synchronizing multiple configurations, such as this low-level task, should be done through code, not manual operations. Python is perfectly capable of parsing .env files.

More importantly, this approach does not elegantly support CI (Continuous Integration). With your current implementation, I would either have to upload sensitive information like database passwords in the code to the repository or have local code outside the scope of the repository in my local deployment environment, which is quite troublesome to maintain. Whether it's GitHub, Vercel, or many other platforms, they all support configuring environment variables (for example: https://github.com/tiwater/ragflow/settings/environments, https://github.com/tiwater/ragflow/settings/secrets/actions). Only authorized administrators can manage the environment variables in environments, setting truly critical information like database passwords, which can override the default values in .env. Only in this way can we avoid having code outside of repository management, without worrying about issues like database password leaks through code, and seamlessly support the major platforms currently in vogue, achieving CI (continuous integration).

As an open-source project with goals, please actively follow best practices.

Describe implementation you've considered

No response

Documentation, adoption, use case

No response

Additional information

No response