How to organize the development process in python (django)?

Question

Django

Hello.
Please help me figure out how to organize the development of a project in janga. I have no experience of participating in combat projects and it is difficult for me to independently understand how to build the development process.
What has been done:
Rented a node with ubuntu
Installed python/django/gunicorn/postgresql/nginx
Everything is set up, everything is running
This node is essentially my production. Let's say that I don't need a sandbox (test server) and I want to immediately see the results in production. Actually, I want to understand how to organize it correctly, so the questions are:
1) Do I need to install an editor like pycharm or vs code on my computer and remotely connect to the node so that all changes take place there right away? If so, how do you fit a git in here?
2) Or is nonsense written in the first paragraph and it somehow needs to be organized through git? I just often stumble upon "I made a commit, everything worked at once in production", I would like to understand how it all works, in particular regarding dzhanga.
And just in case, I’ll ask - Windows is on the home computer, can it somehow interfere with the development process?
Comrades devops and developers, please conduct an educational program, thank you in advance!

Answer 1

You can look here, for example: https://www.digitalocean.com/community/tutorials/h... . The article is old, but gives a general idea.
1. You should set up a test environment on your computer so that you can check that everything starts up before setting up anything at all on the server - it's easier and faster. As for the editor, it all depends on your preferences, even in a notepad if convenient. VS Code is very popular right now and has built-in support for GIT, which is handy if you don't want to bother using it from the console.
2. In a nutshell, you create a project locally - run it, test that everything works - push it to your project repository, pull all updates on the server and run it. Then repeat if necessary. It makes no sense to develop immediately on a remote node.
PS If anything, I'm not a web developer, so maybe now they have come up with something more interesting.