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
Add custom requirements to docker compose #528
Conversation
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Pull Request Test Coverage Report for Build 3437492834
💛 - Coveralls |
Why is postgres-14 the one we should pin? It only happened to be the one you are using. I still think it's better than using the latest always, but this will then become outdated in a while. Maybe we need to think more about how we can pin down what FlexMeasures should support here and how to formalize that. |
It's currently the most recent that didn't throw errors (for me) when running |
Maybe it's an edge case that you created data in your own installation, then want to run it in another, docker-based one. But maybe it'll happen more often. I agree that being specific is a little better, but the drawback is that this needs to be kept up-to-date, the one with a version not. |
This reverts commit 220aa15.
Signed-off-by: F.N. Claessen <felix@seita.nl>
…ts-to-docker-compose
Signed-off-by: F.N. Claessen <felix@seita.nl>
To do:
requirements.txt
file to theflexmeasures-instance
folder.