Local development and Docker?

Question

Web development

I use poppy. Now I am developing sites without vargrant or docker. Simple and collective-farm: I use regular hosting as a dev server. That is not even locally. On a very small project, I’m just sawing on the sale, God forgive me. Locally I keep only php. Basically, because of the composer, so that there is navigation through the vendor code. Well, a gallp for minification and other things. Git yet.
There is always a feeling that everything is crooked. That normal people don't do that. I would like to level up somehow.
Vagrant annoys me with the fact that you need to run a whole virtual machine when your poppy can do it all without it. There is a touch of redundancy.
I liked the docker idea better. There are a couple of questions before I start to study thoroughly:

1. Are all development applications usually used in containers? For example, I have composer, git, node, npm installed globally (as well as less, sass, typescript compliler, gulp packages). Well, PHP is there with its own versions, but these are usually backward compatible and do not require keeping a zoo of versions. Yes, and PhpStorm can be configured once by specifying the path in Git, node, File Watchers. After all, with the docker, should I specify all these minifiers and composers again on each project?
   
2. Is it really justified to use Docker by one or a small group? Perhaps my projects are not of such a level, but it's really not critical for me to recreate the dev and prod environment 1 in 1. The clients are not large, there is no high-load. Well, let php 5.6 spin there on the battlefield, when I have 7.1. In a storm, the language-level can be lowered so as not to flog jambs at all. Or is it better to immediately get used to the good? And if you are developing from scratch and don't know what the configuration will be on the battlefield?
   
3. Is deployment really so simple that it replaces all ftp uploads, jenkins, git pulls? I read on habre.
   

Answer 1

1. GIT is not directly related to the environment for your code, so it makes sense to use it globally. But all sorts of composer / php / node / gulp / yarn / ... are part of the environment for execution, and it is better to keep them right in the container.
However, a specific project is written for a specific version of the interpreter and tested on it, so you should not use it globally.
It's true.
Yes
Yes. For example, you want to look at a project a year ago, but the backward compatibility of your project's dependencies is lost, this is very common.
Nobody creates 1 in 1, but it is as similar as possible in terms of the technology stack - that's right.
There is no sense in such an environment. Your code will work differently, on a production server and in a virtual environment.
You can make demands on combat.
Not

Answer 2

I suggest you take a closer look at the Laradock project
Allows you to not depend on the OS and keep it clean (no development services except for the IDE)
You will quickly understand what is happening. Perhaps you will discover a couple of useful services.