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

Is such a Dockerfile recipe useful? #1

Open
ThomasRoosli opened this issue Sep 12, 2024 · 1 comment
Open

Is such a Dockerfile recipe useful? #1

ThomasRoosli opened this issue Sep 12, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@ThomasRoosli
Copy link
Collaborator

In the branch https://github.com/CLIMADA-project/climada-container/tree/initial_dockerfile we just published a recipe how a containerized application based on the CLIMADA library could be setup. This recipe is similar to the solution developed at MeteoSwiss) and I would like to thank all the dedicated people involved.
We hope that such a recipe might be useful for others, and that we can jointly maintain such a containerization in the future.

Please try it out by following the process described in the README.

Is such a recipe useful for you?
Would you be able to help maintain such a recipe?

@ThomasRoosli ThomasRoosli added the question Further information is requested label Sep 12, 2024
@ThomasRoosli ThomasRoosli self-assigned this Sep 12, 2024
@bguillod
Copy link

Thanks @ThomasRoosli for the recipe!

I find it very relevant and useful. However in the readme I am missing the following information: How where the two required files (poetry.lock and pyproject.toml) generated?

And, as a natural follow up or closely related question: What are the steps to update those two files and, thereby, the environment at regular intervals (including but not limited to when new climada versions are released)?

There are some files that you pre-download (shapefiles for countries) or copy (e.g. catropy data) - can you specify whether these are specifically needed for your case and each user would need to decide which kind of files they need, or whether everyone would need those, specifically?

Last question, my assumption is that you will not (and noone else currently) maintain this (and, hence, update those files, etc) - is this correct?

That being said, I think your recipe already provides a good basis for anyone willing to take this over. This is highly appreciated, many thanks for sharing! Are you intending to do a PR out of it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants