-
Notifications
You must be signed in to change notification settings - Fork 130
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 refactoring #522
base: develop
Are you sure you want to change the base?
Docker refactoring #522
Conversation
45fe7c5
to
53ab0b1
Compare
Maybe this example could help: https://gitmemory.com/issue/sdispater/poetry/366/488720509 |
- "3.7" | ||
- "3.7-dev" # 3.7 development branch | ||
install: | ||
- pip install -r requirements.txt --no-cache | ||
- pip install poetry |
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.
From the poetry docs, the recommended method to install poetry is not to use pip rather their own script
@Mec-iS I can work on this if you aren't |
sorry for the late reply. You don't need to ask for permission. You can just follow the Github Flow and open a PR. |
This PR implement Poetry for Docker and get rid of
requirements.txt
. This will avoid dependencies conflicts from now on thanks to the lock file.I am not 100% sure the
Dockerfile
is done correctly, please trydocker-compose up --build
locally and provide suggestions about how to make this working/safer/more stable.