-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add docker-compose to run Khan locally #61
Conversation
strings.ReplaceAll was removed from go 1.11 and it's making the CI pipeline to break
docker-compose.yml
Outdated
retries: 3 | ||
|
||
networks: | ||
khan: |
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.
A suggestion: we could use the same network name for all services, to help us to integrate with other services (this is why I named the network as wildlife-services
in other services).
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.
Great.
docker-compose.yml
Outdated
build: | ||
context: . | ||
dockerfile: Dockerfile | ||
command: "make migrate" |
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.
Using this configuration with a docker-compose up
without reading README, migrate
and khan
will be running concurrently. Could we have problems with the khan
container due to this?
Which is the advantage of running migrate
outside the khan
container?
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.
Good point. I can override the command to execute both make commands instead of using two separated services.
Closed, done at #72 |
This PR sets up the necessary infrastructure for one to try the project in their local environment.