search

yoheinakajima / babyagi

MIT License
19.9k stars 2.61k forks source link

Feature: Improve configuration management by using YAML and optionally keeping API keys in environment variables #138

Open stepsal opened 1 year ago

stepsal commented 1 year ago

The current configuration management in the project relies on the .env file for managing both configuration and environment variables. As the project grows, the .env file and related validation code will become cluttered and difficult to maintain. Additionally, task prompts and prompt templates could be moved out to a YAML file for enhanced configurability.

To improve organization and maintainability, there could be a couple of approaches

Option 1: Keep API keys in environment variables and move the rest of the configuration to YAML. Option 2: Move all configurations, including API keys, to the YAML file.

Before proceeding with any further requirements, I would like to discuss other users and consider all options to make the best decision for the project. Has this issue been previously raised? Is there a Discord channel where this could be talked about?

stepsal commented 1 year ago

Ill leave this here as reference. https://github.com/sw5park/Otto/blob/main/configs/config.yaml