Refactor backend docker environment towards a python flask backend

[ctmbl]

I simply refactored the Dockerfile and replace any use of node-* by backend-* or flask-*, for example for container name, env variable etc, I also added a requirements.txt for obvious reasons.

To go further:
I chose flask as future python backend framework out of these propositions

Two parts of a DigitalOcean flask tutorial, we could find useful:

• setup a basicflask app part 1/13
• integrate MongoDB to flask part 8/13

Currently the only thing that can be done is run the docker-compose command described in the README.md, without certificates (raw HTTP, after reverting #34 with git revert 8087def for example), and it builds and run without errors. Of course, none of the endpoints the frontend try to reach are currently implemented, it doesn't even use the right port, but this setup the environment to build upon!

We have 3 solutions described to configure the port:

• use of special flask env var on StackOveflow or on DigitalOcean's tuto --> the one we should use according to me
• run the app from app.py in python (doesn't use flask CLI) --> reliable but seems like a hacky solution 🤷
• command line flags --> we shouldn't use that because it changes the docker image according to me

But all this will be work for other PRs to backend/python

⚠️ IMPORTANT: i've read everywhere that the way I currently run the server (flask run) is not the proper way to do it in production, will have to investigate further! (for example serve flask with Gunicorn and Nginx)

[atxr]

Just nitpicking 🙂

[atxr]

🚀

[amtoine]

lgtm 👍

[amtoine]

Note
once we land #91 and the prettier pipeline is fixed, you can

git fetch iscsc
git merge iscsc/main
git push ctmbl

to resolve the conflicts if any @ctmbl 👍

[ctmbl]

@amtoine ofc I'll do it, anyway the CI won't pass if I don't 👍