Add missing dagda envs to compose yml and expand readme #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
READY
Description
Using docker-compose and interacting with Dagda (on Ubuntu at least) used to error out due to ENV variables not being set. These set it in the docker-compose YAML spec so there are no issues. Also added example commands for interacting with dagda using docker exec
Related PRs
N/A
TO-DOs
Deploy Notes
Will just need to restart docker-compose on the host machine after pulling the latest from mainline
Impacted Areas in Application
List general components of the application that this PR will affect: