Closed alexlovelltroy closed 3 months ago
Secrets can be added via ENV variables or files on the host Files on the host can be plaintext files and can be added as secrets and used by services in the compose file. Secret as a file example below
compose.yaml
version: '3.8' services: web: image: <service-container> secrets: - secret-file secrets: secret-file: file: <path to file>
This can be a complex file and the syntax and structure will be preserved.
Here is an example of how we might use files to bring in the ochami-init config file
ochami-init
version: '3.8' smd-init: container_name: smd-init image: ghcr.io/openchami/smd:v2.13.5 environment: - SMD_DBHOST=postgres - SMD_DBPORT=543 - SMD_DBUSER=ochami - SMD_DBPASS=${POSTGRES_PASSWORD} # Set in .env file - SMD_DBNAME=ochami - SMD_DBOPTS=sslmode=disable - OCHAMI_CONFIG=/run/secrets/ochami.yaml #need to read from here now hostname: smd-init depends_on: - postgres - ochami-init networks: - internal entrypoint: - /smd-init secrets: ochami-config secrets: ochami-config: file: deployment-recipes/lanl/docker-compose/configs/ochami.yaml
Secrets can be added via ENV variables or files on the host Files on the host can be plaintext files and can be added as secrets and used by services in the compose file. Secret as a file example below
compose.yaml
This can be a complex file and the syntax and structure will be preserved.
Here is an example of how we might use files to bring in the
ochami-init
config file