Until now the backend had a simple requirements.txt and a script I had written for package/environment management. I think we should move to an actual manager like Poetry.
This will allow us to use the dependencies graph on GitHub, which I think we will really need later on when working on the docs since we will need to add licenses.
The frontend already uses a supported manager, NuGet; and the backend is already structured according to Poetry's requirements. All that's needed is initializing the project, moving the dependencies, and updating the script. This guide should cover all we need.
Poetry also uses virtual environments so the isolation benefit of containerization (#22) won't be as important.
Until now the backend had a simple
requirements.txt
and a script I had written for package/environment management. I think we should move to an actual manager like Poetry.This will allow us to use the dependencies graph on GitHub, which I think we will really need later on when working on the docs since we will need to add licenses.
The frontend already uses a supported manager, NuGet; and the backend is already structured according to Poetry's requirements. All that's needed is initializing the project, moving the dependencies, and updating the script. This guide should cover all we need.
Poetry also uses virtual environments so the isolation benefit of containerization (#22) won't be as important.