-
Version InformationServer Version: EnvironmentEE What is the current behaviour?hasura ee container ONLY take configuration properties from environment variables What is the expected behaviour?expect to load hasura configuration properties, especially hasura_adminm_secret from file instread of ONLY from environment variables in container setup How to reproduce the issue?Screenshots or ScreencastPlease provide any traces or logs that could help here.Any possible solutions?Can you identify the location in the source code where the problem exists?If the bug is confirmed, would you be willing to submit a PR?Keywords |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You can pass the env vars from a file (and specify the file in the docker compose). Here is a sample docker compose file (see highlighted env_file section): ` version: '3.6' ` ` ` Let us know if this answers your question. |
Beta Was this translation helpful? Give feedback.
You can pass the env vars from a file (and specify the file in the docker compose).
Here is a sample docker compose file (see highlighted env_file section):
`
docker-compose.yml
version: '3.6'
services:
postgres:
image: postgres:12
restart: always
volumes:
- db_data:/var/lib/postgresql/data
environment:
POSTGRES_PASSWORD: postgrespassword
graphql-engine:
image: hasura/graphql-engine:v2.11.0
ports:
- "8080:8080"
depends_on:
- "postgres"
restart: always
env_file:
- ./test_env_vars.test
volumes:
db_data:
`
You can then add all your env vars in test_env_vars.test (used for illustration, please use a name suitable for your use):
`
test_env_vars.test
environment:
## postgres database to store H…