-
Notifications
You must be signed in to change notification settings - Fork 79
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
Cleanup of .env content; Add debezium/perf. #1970
Conversation
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 was under the assumption you'd be removing our docker deploy resource limits - was that going to be separate?
I do want to take the time Monday and run the compose file myself.
Somehow I lost that change; done. |
…and mysql, to allow more events per second.
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.
Let's give @niloc132 a chance; and I still want to take a pass at running it soon.
|
||
mysql: | ||
image: debezium/example-mysql:1.4 | ||
ports: | ||
- 3306:3306 | ||
- 3306:3306 |
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.
after the fact review: prefer quotes for these (like you did in line 49) since yaml can do some super awesome type coercion when it doesn't know what you might be trying to express
On
.env
files:Simplify memory configuration for the server definition in
docker-compose-common.yml
.