-
Notifications
You must be signed in to change notification settings - Fork 45.8k
fix(platform): load env vars in docker compose #10036
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for auto-gpt-docs-dev canceled.
|
✅ Deploy Preview for auto-gpt-docs canceled.
|
Here's the code health analysis summary for commits Analysis Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR aims to DRY the reference to the .env file in the Supabase Docker Compose configuration by introducing a YAML anchor.
- Introduces a top-level YAML anchor (x-envfile) to avoid repeated .env file configuration across services.
- Applies the merge key (<<: *env_file) to multiple service definitions to include the shared env_file configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is it used for? should we include backend/.env too ?
@majdyz this was an attempt to make it so docker reads and uses the proper .env files, i asked codex to help fix it, im going to test it and see if it works + yeah i can make it use backend/.env |
Summary
.env
reference in Supabase docker-compose using YAML anchorTesting
poetry run format
poetry run test
(fails: FileNotFoundError: [Errno 2] No such file or directory: 'docker')yarn format
yarn test
(fails: Failed to fetchPoppins
from Google Fonts)