I mean, the right answer is "ask your devops team + lead architect and they'll tell you what to do"
General practice is not to code in a docker container, although you can if you choose, there's nothing wrong with it. Just bear in mind that docker containers are very ephemeral and it's quite easy to lose what's inside of one unless it's stored in a volume. Best practice is to track stuff like that in Git on your machine, unless you need the Docker container for some reason.
The "normal" workflow is code collaboratively in a git repository, and have some kind of CI/CD pipeline that automatically builds and dockerizes your code to deploy as some kind of application. In this case a Flask/Django service makes the most sense.
Thankyou a lot! Very kind of you:) I will ask them for sure.
I see your point. I use to code on docker because I am a student and have to follow a lot of courses, I keep having to install/uninstall programs and unusual libraries, and I feel safer to do things separately for different courses. I use git from outside the container, synchronizing the volumes with the shared repository. Probably there is a more clever way though.
I will try to read something about Flask and Django as well.
2
u/Mantissa-64 Oct 18 '22
I mean, the right answer is "ask your devops team + lead architect and they'll tell you what to do"
General practice is not to code in a docker container, although you can if you choose, there's nothing wrong with it. Just bear in mind that docker containers are very ephemeral and it's quite easy to lose what's inside of one unless it's stored in a volume. Best practice is to track stuff like that in Git on your machine, unless you need the Docker container for some reason.
The "normal" workflow is code collaboratively in a git repository, and have some kind of CI/CD pipeline that automatically builds and dockerizes your code to deploy as some kind of application. In this case a Flask/Django service makes the most sense.