Skip to content

Conversation

@Manan007224
Copy link

@Manan007224 Manan007224 commented Nov 9, 2021

I am fixing two things in this PR

  • README.md for specs - This file had references to some redundant scripts which we don't exists anymore and also added references in respect to our new docker-compose based setup.

  • proxysql setup via docker-compose.

dev.yml Outdated
name: Waiting for DBs to be operational
met?: ./scripts/helpers/wait-for-dbs.sh
meet: ":"
meet: docker-compose up -d
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The above two steps felt like they could be merged into one. I mean in the end after setting up docker-compose we want to see if the local test containers are up or not.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't this make it run a lot slower? It will try to met? which will take a whole long time to timeout (If there is a timeout), then it will create the docker-compose. I set it up in this order with a "no-op" to ensure that the containers are at least warming up when the script starts

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you try to run this with the docker-compose being down? Or did you run it when it was already up?

logs:
desc: "See the DB logs (ctrl-c + ctrl-c to exit)"
run: docker-compose logs -f
mysql:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a really good addition 👍

Copy link

@EtienneBerubeShopify EtienneBerubeShopify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few things to clarify, but overall looks good 👍

proxysql:
host: proxysql
user: root
user: remote-admin

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this should be changed. This file is used to connect to the underlying database and not the admin. I added these changes when changing the test environment, but the changes are only used in #112

threads=8
max_connections=100000
interfaces="0.0.0.0:3306"
interfaces="0.0.0.0:6033"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't we want to be able to communicate with MySQL on port 3306? So that everything is consistent?

Copy link

@EtienneBerubeShopify EtienneBerubeShopify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: little question about port selection, but other than that LGTM 👍

Copy link

@EtienneBerubeShopify EtienneBerubeShopify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

changes

changes

changes

changes

changes

fix tests

changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants