What is the best way to organize a working environment for a web developer?

Question

PHP

Now I work on Windows and always install separately apache, php, postgreSQL + various modules. I do not use openserver and other assemblies because there are problems with them. I would like to have a configuration close to production.
I see the following ways:
1. Work in the environment of the Linux system, as the main one.
2. Put Linux in the virtual machine and deploy the server there. Open access to the host machine. (didn't do it).
Will I get a lot of problems with fishing in Linux as a full stack developer.?
Or are there other ways? How do you work?

Answer 1

Start with a virtual machine, and then you will understand

Answer 2

Well, here without options - a virtual machine.
There are such solutions:
- Use the built-in Windows WSL. By installing, for example, Ubuntu from the Windows store. An inferior system, but more than enough for a web developer.
- Roll the system into Hyper-V, VMware or VirtualBox yourself.
- Vagrant
- Docker for Windows. It can also be manually put into the system in the second method. WSL will not work.
In general, if you only need an environment, then I advise Docker. And if the goal is to gain advanced knowledge in setting up services - the second way. I myself am a fullstack developer, and I develop a little towards devops. In the case of Docker, it is easy to raise different services of different versions for testing, especially if you plan to go beyond apache+php+db. For example redis, rabbitmq, elastic search, node.

Answer 3

Install linux (ubuntu, mint - good for a first acquaintance after Windows) and docker. When I switched from Windows, I was looking for analogues of openserver, I tried vagrant, phpbrew - everything is extremely inconvenient. Then they talked about docker and immediately fell in love. A little later, I wrote a small script with which you can deploy any web environment with one command: php 5.6-7.3, apache / nginx, mysql 5.6-5.7 and in a few minutes a working local site will appear. If interested, I can give a link to github

Answer 4

I've gone through these paths ... as a former Windows administrator, I mostly sit on Windows (including now), but for a developer, any * nix system is better, whether it's poppy or Linux (I sat in each option for at least year) ... there will be much less problems with them than with Windows
Manuals are all written under * nix, all software is sharpened under nix, configs only work there without problems
What I encountered in Windows:
1) Docker for windows - I managed to pile up only sacrificing virtualbox 3-4 times and having a bunch of rake when, after updating Windows, it dies along with hyper-v on the basis of which it works (and eats RAM like crazy)
2) If you accidentally save a file with a config / code with windbreaks ... it will be fun to look for it ... when visually everything is ok, but nothing works and it’s not clear why and where
3) It’s even more fun if two file with the same names in different registers ... I puzzled for a very long time why there is one thing in the file, and another in the stack trace ... it's not linux with a case-sensitive FS
why I returned to Windows: all the same, no matter how Linuxoids throw slippers, but Windows has a more organic gui, but I never learned how to live in the console and cry with happiness (although I managed to work as a Linux admin for quite a long time and successfully) ... and when WSL was brought there, the vast majority of the problems disappeared (except for 3x above)
therefore, if there is no special desire and knowledge in the innards of Windows, you need to sit on Linux, it is both more useful and convenient and it will take less time to search for all sorts of strange jambs about which they do not write in the documentation (because normal people do not write software under Windows that works in nixah)

Answer 5

If there is time to red-eye then Linux, if not, then Mac

Answer 6

In windows, after mastering the virtual machine, the vast majority of problems disappear. Plus, docker is a must because it's the best way to create an environment... multi-environment.
About docker and windows. "Special" tools, such as docker for windows, are not required. You create a regular Linux virtual machine (I use debian) and run docker, everything works without problems.
Plus, install a fancy console like Cmder and you have a comfortable environment in a vacuum.