2023-04-13 16:13:32 +00:00
|
|
|
################################################################################
|
|
|
|
|
### AUTO-GPT - GENERAL SETTINGS
|
|
|
|
|
################################################################################
|
2023-04-19 00:04:11 +00:00
|
|
|
|
|
|
|
|
## EXECUTE_LOCAL_COMMANDS - Allow local command execution (Default: False)
|
|
|
|
|
## RESTRICT_TO_WORKSPACE - Restrict file operations to workspace ./auto_gpt_workspace (Default: True)
|
2023-04-18 21:40:43 +00:00
|
|
|
# EXECUTE_LOCAL_COMMANDS=False
|
2023-04-19 00:04:11 +00:00
|
|
|
# RESTRICT_TO_WORKSPACE=True
|
2023-04-18 21:40:43 +00:00
|
|
|
|
|
|
|
|
## BROWSE_CHUNK_MAX_LENGTH - When browsing website, define the length of chunk stored in memory
|
|
|
|
|
# BROWSE_CHUNK_MAX_LENGTH=8192
|
|
|
|
|
|
|
|
|
|
## USER_AGENT - Define the user-agent used by the requests library to browse website (string)
|
2023-04-13 22:45:41 +00:00
|
|
|
# USER_AGENT="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
|
2023-04-18 21:40:43 +00:00
|
|
|
|
|
|
|
|
## AI_SETTINGS_FILE - Specifies which AI Settings file to use (defaults to ai_settings.yaml)
|
|
|
|
|
# AI_SETTINGS_FILE=ai_settings.yaml
|
|
|
|
|
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
################################################################################
|
|
|
|
|
### LLM PROVIDER
|
|
|
|
|
################################################################################
|
|
|
|
|
|
|
|
|
|
### OPENAI
|
2023-04-18 21:40:43 +00:00
|
|
|
## OPENAI_API_KEY - OpenAI API Key (Example: my-openai-api-key)
|
|
|
|
|
## TEMPERATURE - Sets temperature in OpenAI (Default: 0)
|
|
|
|
|
## USE_AZURE - Use Azure OpenAI or not (Default: False)
|
2023-04-03 21:29:55 +00:00
|
|
|
OPENAI_API_KEY=your-openai-api-key
|
2023-04-18 21:40:43 +00:00
|
|
|
# TEMPERATURE=0
|
|
|
|
|
# USE_AZURE=False
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
2023-04-13 16:13:32 +00:00
|
|
|
### AZURE
|
2023-04-18 21:40:43 +00:00
|
|
|
# moved to `azure.yaml.template`
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
################################################################################
|
|
|
|
|
### LLM MODELS
|
|
|
|
|
################################################################################
|
|
|
|
|
|
2023-04-18 21:40:43 +00:00
|
|
|
## SMART_LLM_MODEL - Smart language model (Default: gpt-4)
|
|
|
|
|
## FAST_LLM_MODEL - Fast language model (Default: gpt-3.5-turbo)
|
|
|
|
|
# SMART_LLM_MODEL=gpt-4
|
|
|
|
|
# FAST_LLM_MODEL=gpt-3.5-turbo
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
### LLM MODEL SETTINGS
|
2023-04-18 21:40:43 +00:00
|
|
|
## FAST_TOKEN_LIMIT - Fast token limit for OpenAI (Default: 4000)
|
|
|
|
|
## SMART_TOKEN_LIMIT - Smart token limit for OpenAI (Default: 8000)
|
|
|
|
|
## When using --gpt3only this needs to be set to 4000.
|
|
|
|
|
# FAST_TOKEN_LIMIT=4000
|
|
|
|
|
# SMART_TOKEN_LIMIT=8000
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
################################################################################
|
|
|
|
|
### MEMORY
|
|
|
|
|
################################################################################
|
|
|
|
|
|
2023-04-15 21:26:42 +00:00
|
|
|
### MEMORY_BACKEND - Memory backend type
|
2023-04-18 21:40:43 +00:00
|
|
|
## local - Default
|
|
|
|
|
## pinecone - Pinecone (if configured)
|
|
|
|
|
## redis - Redis (if configured)
|
|
|
|
|
## milvus - Milvus (if configured)
|
|
|
|
|
## MEMORY_INDEX - Name of index created in Memory backend (Default: auto-gpt)
|
|
|
|
|
# MEMORY_BACKEND=local
|
|
|
|
|
# MEMORY_INDEX=auto-gpt
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
### PINECONE
|
2023-04-18 21:40:43 +00:00
|
|
|
## PINECONE_API_KEY - Pinecone API Key (Example: my-pinecone-api-key)
|
|
|
|
|
## PINECONE_ENV - Pinecone environment (region) (Example: us-west-2)
|
|
|
|
|
# PINECONE_API_KEY=your-pinecone-api-key
|
|
|
|
|
# PINECONE_ENV=your-pinecone-region
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
### REDIS
|
2023-04-18 21:40:43 +00:00
|
|
|
## REDIS_HOST - Redis host (Default: localhost, use "redis" for docker-compose)
|
|
|
|
|
## REDIS_PORT - Redis port (Default: 6379)
|
|
|
|
|
## REDIS_PASSWORD - Redis password (Default: "")
|
|
|
|
|
## WIPE_REDIS_ON_START - Wipes data / index on start (Default: False)
|
|
|
|
|
# REDIS_HOST=localhost
|
|
|
|
|
# REDIS_PORT=6379
|
|
|
|
|
# REDIS_PASSWORD=
|
|
|
|
|
# WIPE_REDIS_ON_START=False
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
2023-04-15 05:51:04 +00:00
|
|
|
### WEAVIATE
|
2023-04-18 21:40:43 +00:00
|
|
|
## MEMORY_BACKEND - Use 'weaviate' to use Weaviate vector storage
|
|
|
|
|
## WEAVIATE_HOST - Weaviate host IP
|
|
|
|
|
## WEAVIATE_PORT - Weaviate host port
|
|
|
|
|
## WEAVIATE_PROTOCOL - Weaviate host protocol (e.g. 'http')
|
|
|
|
|
## USE_WEAVIATE_EMBEDDED - Whether to use Embedded Weaviate
|
|
|
|
|
## WEAVIATE_EMBEDDED_PATH - File system path were to persist data when running Embedded Weaviate
|
|
|
|
|
## WEAVIATE_USERNAME - Weaviate username
|
|
|
|
|
## WEAVIATE_PASSWORD - Weaviate password
|
|
|
|
|
## WEAVIATE_API_KEY - Weaviate API key if using API-key-based authentication
|
|
|
|
|
# WEAVIATE_HOST="127.0.0.1"
|
|
|
|
|
# WEAVIATE_PORT=8080
|
|
|
|
|
# WEAVIATE_PROTOCOL="http"
|
|
|
|
|
# USE_WEAVIATE_EMBEDDED=False
|
|
|
|
|
# WEAVIATE_EMBEDDED_PATH="/home/me/.local/share/weaviate"
|
|
|
|
|
# WEAVIATE_USERNAME=
|
|
|
|
|
# WEAVIATE_PASSWORD=
|
|
|
|
|
# WEAVIATE_API_KEY=
|
2023-04-15 05:51:04 +00:00
|
|
|
|
2023-04-11 11:36:41 +00:00
|
|
|
### MILVUS
|
2023-04-18 21:40:43 +00:00
|
|
|
## MILVUS_ADDR - Milvus remote address (e.g. localhost:19530)
|
2023-04-19 00:04:11 +00:00
|
|
|
## MILVUS_COLLECTION - Milvus collection,
|
2023-04-18 21:40:43 +00:00
|
|
|
## change it if you want to start a new memory and retain the old memory.
|
|
|
|
|
# MILVUS_ADDR=your-milvus-cluster-host-port
|
|
|
|
|
# MILVUS_COLLECTION=autogpt
|
2023-04-11 11:36:41 +00:00
|
|
|
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
################################################################################
|
|
|
|
|
### IMAGE GENERATION PROVIDER
|
|
|
|
|
################################################################################
|
|
|
|
|
|
|
|
|
|
### OPEN AI
|
2023-04-18 21:40:43 +00:00
|
|
|
## IMAGE_PROVIDER - Image provider (Example: dalle)
|
2023-04-19 00:51:22 +00:00
|
|
|
## IMAGE_SIZE - Image size (Example: 256)
|
|
|
|
|
## DALLE: 256, 512, 1024
|
2023-04-18 21:40:43 +00:00
|
|
|
# IMAGE_PROVIDER=dalle
|
2023-04-19 00:51:22 +00:00
|
|
|
# IMAGE_SIZE=256
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
### HUGGINGFACE
|
2023-04-19 00:51:22 +00:00
|
|
|
## HUGGINGFACE_IMAGE_MODEL - Text-to-image model from Huggingface (Default: CompVis/stable-diffusion-v1-4)
|
2023-04-18 21:40:43 +00:00
|
|
|
## HUGGINGFACE_API_TOKEN - HuggingFace API token (Example: my-huggingface-api-token)
|
2023-04-19 00:51:22 +00:00
|
|
|
# HUGGINGFACE_IMAGE_MODEL=CompVis/stable-diffusion-v1-4
|
2023-04-18 21:40:43 +00:00
|
|
|
# HUGGINGFACE_API_TOKEN=your-huggingface-api-token
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
2023-04-18 23:30:28 +00:00
|
|
|
### STABLE DIFFUSION WEBUI
|
2023-04-19 00:51:22 +00:00
|
|
|
## SD_WEBUI_AUTH - Stable diffusion webui username:password pair (Example: username:password)
|
|
|
|
|
## SD_WEBUI_URL - Stable diffusion webui API URL (Example: http://127.0.0.1:7860)
|
|
|
|
|
# SD_WEBUI_AUTH=
|
|
|
|
|
# SD_WEBUI_URL=http://127.0.0.1:7860
|
2023-04-18 23:30:28 +00:00
|
|
|
|
2023-04-15 21:19:20 +00:00
|
|
|
################################################################################
|
|
|
|
|
### AUDIO TO TEXT PROVIDER
|
|
|
|
|
################################################################################
|
|
|
|
|
|
|
|
|
|
### HUGGINGFACE
|
2023-04-18 21:40:43 +00:00
|
|
|
# HUGGINGFACE_AUDIO_TO_TEXT_MODEL=facebook/wav2vec2-base-960h
|
2023-04-15 21:19:20 +00:00
|
|
|
|
2023-04-14 01:03:19 +00:00
|
|
|
################################################################################
|
|
|
|
|
### GIT Provider for repository actions
|
|
|
|
|
################################################################################
|
|
|
|
|
|
|
|
|
|
### GITHUB
|
2023-04-18 21:40:43 +00:00
|
|
|
## GITHUB_API_KEY - Github API key / PAT (Example: github_pat_123)
|
|
|
|
|
## GITHUB_USERNAME - Github username
|
|
|
|
|
# GITHUB_API_KEY=github_pat_123
|
|
|
|
|
# GITHUB_USERNAME=your-github-username
|
2023-04-14 01:03:19 +00:00
|
|
|
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
################################################################################
|
2023-04-18 14:01:45 +00:00
|
|
|
### WEB BROWSING
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
################################################################################
|
|
|
|
|
|
2023-04-18 14:01:45 +00:00
|
|
|
### BROWSER
|
2023-04-19 16:19:39 +00:00
|
|
|
## HEADLESS_BROWSER - Whether to run the browser in headless mode (default: True)
|
2023-04-19 00:04:11 +00:00
|
|
|
## USE_WEB_BROWSER - Sets the web-browser driver to use with selenium (default: chrome).
|
|
|
|
|
## Note: set this to either 'chrome', 'firefox', or 'safari' depending on your current browser
|
2023-04-19 16:19:39 +00:00
|
|
|
# HEADLESS_BROWSER=True
|
2023-04-18 14:15:37 +00:00
|
|
|
# USE_WEB_BROWSER=chrome
|
2023-04-18 14:01:45 +00:00
|
|
|
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
### GOOGLE
|
2023-04-18 21:40:43 +00:00
|
|
|
## GOOGLE_API_KEY - Google API key (Example: my-google-api-key)
|
|
|
|
|
## CUSTOM_SEARCH_ENGINE_ID - Custom search engine ID (Example: my-custom-search-engine-id)
|
|
|
|
|
# GOOGLE_API_KEY=your-google-api-key
|
|
|
|
|
# CUSTOM_SEARCH_ENGINE_ID=your-custom-search-engine-id
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
|
|
|
|
################################################################################
|
|
|
|
|
### TTS PROVIDER
|
|
|
|
|
################################################################################
|
|
|
|
|
|
|
|
|
|
### MAC OS
|
2023-04-18 21:40:43 +00:00
|
|
|
## USE_MAC_OS_TTS - Use Mac OS TTS or not (Default: False)
|
|
|
|
|
# USE_MAC_OS_TTS=False
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
|
2023-04-14 03:47:21 +00:00
|
|
|
### STREAMELEMENTS
|
2023-04-18 21:40:43 +00:00
|
|
|
## USE_BRIAN_TTS - Use Brian TTS or not (Default: False)
|
|
|
|
|
# USE_BRIAN_TTS=False
|
2023-04-14 06:28:47 +00:00
|
|
|
|
Improve .env File Organization, Readability, and Documentation
This pull request aims to enhance the organization, readability, and understanding of the .env.template file for users when they modify the settings. The changes include organizing the file in a tree-like structure with appropriate comments, providing clear guidance for users about the purpose of each variable, their possible values, and default settings when applicable.
As a user with no prior knowledge of best practices of contributing to a project / .env.template file documentation, I took the liberty to make changes to the file based on what I would have liked to have seen when I first encountered it. My goal was to include every configurable option for ease of use and better understanding of how the code works.
The key improvements made in this pull request are:
1. Grouping related variables under appropriate headers for better organization and ease of navigation.
2. Adding informative comments for each variable to help users understand their purpose and possible values.
3. Including default values in the comments to inform users of the consequences of not providing a specific value for a variable, allowing them to make
informed decisions when configuring the application.
4. Formatting the file consistently for better readability.
These changes will enhance user experience by simplifying the configuration process and reducing potential confusion. Users can quickly and easily configure the application without having to search through the code to determine default values or understand the relationship between various settings. Additionally, well-organized code and documentation can lead to fewer issues and misunderstandings, saving time for both users and maintainers of the project.
Please review these changes and let me know if you have any questions or suggestions for further improvement so I can make any necessary adjustments.
2023-04-12 16:54:10 +00:00
|
|
|
### ELEVENLABS
|
2023-04-18 21:40:43 +00:00
|
|
|
## ELEVENLABS_API_KEY - Eleven Labs API key (Example: my-elevenlabs-api-key)
|
|
|
|
|
## ELEVENLABS_VOICE_1_ID - Eleven Labs voice 1 ID (Example: my-voice-id-1)
|
|
|
|
|
## ELEVENLABS_VOICE_2_ID - Eleven Labs voice 2 ID (Example: my-voice-id-2)
|
|
|
|
|
# ELEVENLABS_API_KEY=your-elevenlabs-api-key
|
|
|
|
|
# ELEVENLABS_VOICE_1_ID=your-voice-id-1
|
|
|
|
|
# ELEVENLABS_VOICE_2_ID=your-voice-id-2
|
2023-04-15 21:24:05 +00:00
|
|
|
|
|
|
|
|
################################################################################
|
2023-04-18 21:40:43 +00:00
|
|
|
### TWITTER API
|
2023-04-15 21:24:05 +00:00
|
|
|
################################################################################
|
|
|
|
|
|
2023-04-18 21:40:43 +00:00
|
|
|
# TW_CONSUMER_KEY=
|
|
|
|
|
# TW_CONSUMER_SECRET=
|
|
|
|
|
# TW_ACCESS_TOKEN=
|
|
|
|
|
# TW_ACCESS_TOKEN_SECRET=
|
