-
Notifications
You must be signed in to change notification settings - Fork 7
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
Start integration test #39
Conversation
185558b
to
415f10e
Compare
@@ -0,0 +1,12 @@ | |||
FROM golang:1.5.3 |
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.
I'm planning a base image for testing here, but it is not finished yet: https://hub.docker.com/r/ruflin/beat-testing/
@ruflin Have a look :) A few questions:
|
|
Do you mean sometimes the |
Indeed, the |
It could happen in the past, that a build started to hang so docker-compose stop was never called. Be aware that these are edge cases, but it is what lead to our current implementation. I really like to use "real" nginx to test the stats as it makes it possible to also test different versions. Be aware that |
Yea, I'm aware of that but Nginx keeps stats in memory so we don't have to remove the container. Asking Nginx to reload would also do the trick. |
Perhaps, we could also use |
Good to know about nginx. I was thinking in a more general way how to handle it. --force-recreate would work for nginx but not for services that store data on volumes: docker/compose#2127 |
#35