-
Notifications
You must be signed in to change notification settings - Fork 652
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
docker cleanup #90
docker cleanup #90
Conversation
Motivation: repository currently contains two seperate docker definitions that are confusing to users Modifications: * remove Dockerfile.xenial so we have a canonical docker file for CI and developer testing * point docker compose to canonical docker file * define docker compose services for unit and integration tests. and make "test" service run both * update readme Result: users are less confused about docker setup
Why do we need to remove |
@Lukasa to make docker compose based testing identical to our CI. there is an argument to be made to add tests for both versions, but until we do i prefer to avoid the confusion this can (and did) cause , and allow running integration tests via docker compose which was not possible in the existing version |
yup, that’s what we use in CI |
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.
Ok, please rebase. 😁
@tomerd please rebase and merge. |
Motivation: RFC 7540 requires that HTTP/2 pseudo-headers must be first in a HTTP/2 header block, and must occur before any regular headers. We should enforce that requirement. Modifications: - Added checking that pseudo-headers are first in a header block. Result: Better RFC 7540 validation.
Motivation:
repository currently contains two seperate docker definitions that are confusing to users
Modifications:
Result:
users are less confused about docker setup