Do I understand the basic deployment algorithm correctly?

Question

linux

There will probably be a tough stupidity, please don’t kick me) I’m just studying deploy and git, as I’ve recently been on the web and programming in general.
Reading TDD with Python. Starting from chapter 8, to move forward, you need to have a server that meets the following conditions:
- Your server is running Ubuntu 14.04 (aka "Trusty/LTS")
- You have root access to it.
- It's on the public Internet.
- You can SSH into it.
Do I understand correctly that if I create an account, say, on digitalocean and have a droplet there, then I will have all this? It’s just that you have to pay there and I don’t want to just throw money away.
And in general, I want to understand the deployment process as a whole, otherwise all the manuals start right with setting up the server, not to mention how, in fact, to get hold of this very server. Apparently, this is damn obvious, and explaining such elementary things to any babies is unnecessary =)
What I now understand (or think I understand):
1) At DO, I sort of rent a computer that will be my server, right? Then I install, say, nginx there, and spend a couple of nights and a lot of nerves on setting it up.
2) It will be necessary to upload the sources of my project to the server, for example, by cloning the repository from github. And install dependencies + deal with statics. nginx itself should distribute statics, not django (I use this framework), since it is more efficient.
3) This server will have an IP address through which it will be available to the 'outside world', and it will be possible to bind this IP to the purchased domain.
4) To communicate with the server, it is better to have Linux on the local machine.
It's like that? No details, of course.
I know that there are simple options without all this pandemonium that are suitable for 'playing around'. For example, pythonanywhere. I already tried to throw my project there, everything works, but, of course, that's not it. You need to understand the basics.
It's just that in this book the author does not say anything about this, he also goes straight to setting up the server there.

Answer 1

1) On DO, I sort of rent myself a computer that will be my server, right? Then I install, say, nginx there, and spend a couple of nights and a lot of nerves on setting it up.

Yes.
VPS - This, on the one hand, is something like a virtual machine, a bunch of which can be started / stopped on one physical machine. On the other hand, everything that is said about a lower performance OS in a virtual machine (compared to an OS on live hardware) practically does not apply to VPS (the reason is different virtualization principles).
When developing in an interpreted language, this is inevitable.
Yes.
The server is managed via SSH. OS on the local machine can be any. From under Windows, for example, you can work through PuTTy .

Answer 2

It's still worth kicking your feet... Instead of inventing some strange schemes, take and install the server on a virtual machine. At the same time, learn how to deploy linux.

Answer 3

Look at mne.ru, there are 2 virtual machines there. 256mb ram - 90r / month, 512 - about 170

Answer 4

AWS is completely free. Yes, and experience with Amazon will be useful.