Open Server and own assembly of the local server conflict is inevitable?

Question

open server

Hello guys. A batch local server is certainly good, but I would like to have my own local server assembly in addition. That is, individually downloaded phpmyadmin, php, etc.
My question to you:
1. Will there be conflict between Open Server vs Custom build? I understand that the port can be occupied by one of them, but since I still understand this, I would like to hear your opinion and how to avoid conflict between them?
2. When installing your own server assembly, do you need to download php versions in one package or for each version there is a separate package? Example: The new php 7 includes all previous versions and you can switch between them, How in Open Server?
Thanks for answers :)

Answer 1

Hello, again...
1. I already answered this question in another thread - configure so that different ports are used in assemblies. Moreover, if both assemblies work simultaneously, then port reassignment applies not only to Apache, but also to Mysql, etc. services that will listen to some ports in assemblies.
2. Other (previous) versions cannot be included in php7, that's why it is the 7th version. But, on the server, you can use different branches of php (+ a set of software accompanying them), switching between them, as is done in OpenServer. Therefore, if your assembly needs different versions of php, then you will need to download them separately and then configure your assembly to switch between them.

Answer 2

Let's start by finding out the reason. Why do we need such a zoo on a Windows computer?
Firstly, hosting is mostly unix.
Setting up a stack from php, mysql, appache under Windows can be done once out of interest,
but it coincides with Unix very weakly.
In addition, when developing under Windows, you have to remember about case in file names all the time.
other differences are already in more subtle moments (work with sockets and streams, etc.)
It is more useful to raise centos or debian in a virtual machine.