Skip to content
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

[Improvement]: Implement a separate docker compose file for codeception for more clarity #141

Open
aryaantony92 opened this issue Mar 27, 2023 · 4 comments

Comments

@aryaantony92
Copy link
Contributor

Improvement description

Follow up to #109

@aryaantony92 aryaantony92 added this to the 11.0.0 milestone Mar 27, 2023
@yariksheptykin
Copy link
Contributor

@aryaantony92 could you describe a bit more what you aim for with this improvement? Maybe I can do a PR if you find it helpful.

@yariksheptykin
Copy link
Contributor

Do you what to move these two services into a separate docker-compose.yml? Like docker-compose.test.yml?

@aryaantony92
Copy link
Contributor Author

aryaantony92 commented Apr 27, 2023

@aryaantony92 could you describe a bit more what you aim for with this improvement? Maybe I can do a PR if you find it helpful.

@yariksheptykin Sure, Thank you!

@aryaantony92
Copy link
Contributor Author

aryaantony92 commented Apr 27, 2023

Do you what to move these two services into a separate docker-compose.yml? Like docker-compose.test.yml?

@yariksheptykin Yes exactly. Also, please update the steps in readme that for running codeception, we need to bring up the container with the new docker-composer-test.yaml and then run the codeception command.

@dvesh3 dvesh3 removed this from the 11.0.0 milestone May 8, 2023
@dvesh3 dvesh3 self-assigned this Jun 28, 2023
@dvesh3 dvesh3 removed their assignment Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants