Answer the question
In order to leave comments, you need to log in
Creation of a test environment for website development
Faced such a problem, now one test server is used where one environment is used. A simple lamp server and git on it. I would very much like to make a system where for a particular host it would be possible to specify the PHP version that will work on it, Apache or Enginx or a bunch of them together, the database version and so on. Is there a similar solution that allows you to quickly create and change environments. There is Open Server on the developer hosts, it changes there by simply changing the profile, but the profile changes for all hosts, so I would like to transfer everything to the test server first, and secondly, change environments.
Answer the question
In order to leave comments, you need to log in
Um… Look at Chef, Knife and the like. But, I feel, this is not quite right, and while you implement it, you will turn gray =)
I have multiple test VMs with different server configurations. If necessary, any machine can be easily cloned and put updates or something else there. If you need not an individual, but a shared server, virtual machines can be placed on one of the constantly working computers and made them members of the office network.
I see the creation of a bicycle.
You need to independently assemble all the software versions you need, specifying --prefix=/usr/local/package.version
+ write a script that will assemble all this into a single system (mainly configs with the correct paths) and run this miracle on different ports, and in LAN it is possible and on different ip just.
It will not be difficult to fasten the gui to this on the same php.
The very complexity in the assembly of all these packages.
Otherwise, the easiest way is virtual machines + projects connected via nfs.
You can also automate the installation of software in these virtual machines, based on running data. But all this takes time.
It turns out that with virtual machines it takes less time to start the system in general, but more is required if you need to immediately get some kind of non-standard configuration.
And with locally installed packages with changed paths. We need more time to launch and prepare everything. But then you can quickly get the desired result.
As an option - install proxmox for example. Put projects in storage and mount it as /var/www to your virtual machines. And already on virtual machines, use whatever settings / technologies you like.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question