Fixes issue #1827 where Docker Compose wasn't properly loading .env.local file.
Problem:
- Docker Compose expects .env file for variable substitution but docs say to use .env.local
- This caused environment variables to not be loaded in Docker containers
Solution:
- Updated docker-compose.yaml to load both .env and .env.local files
- Created setup-env.sh script to help users sync .env.local to .env
- Updated documentation with clear instructions for Docker users
- Maintains backward compatibility with existing setups
Changes:
- Modified docker-compose.yaml to use array syntax for env_file
- Added scripts/setup-env.sh helper script
- Updated CONTRIBUTING.md and index.md documentation
This ensures environment variables work correctly in Docker while maintaining
the security best practice of using .env.local for sensitive data.
Contributed by: Keoma Wright
Environment variables are not being passed to the container in the development profile. Adding env_file to pass them so they can be used by the application.
* feat: Integrate AWS Bedrock with Claude 3.5 Sonnet, Claude 3 Sonnet, and Claude 3.5 Haiku
* update Dockerfile for AWS Bedrock configuration
* feat: add new Bedrock model 'Mistral' and update Haiku to version 3
* feat: add new bedrock model Nova Lite and Nova Pro
* Update README documentation to reflect the latest changes
* Add the icon for aws bedrock
* add support for serialized AWS Bedrock configuration in api key
- Create detailed provider implementation guide with:
- Architecture overview and implementation steps
- Configuration patterns and best practices
- Testing checklist and Docker integration guide
- Example using Together AI implementation
- Add Together AI as new provider with:
- Environment variables and Docker configuration
- Support for Qwen, Llama, and Mixtral models
- API key and base URL management
- OpenAI-compatible API integration
