If your current company is a web development company that is isolated from the PHP community (←improving), you assume that a non-PHP programmer will build a Linux server in the production environment.
Based on the assumption above, I have
php-build to the build option with
--with-apxs2=/usr/sbin/apxs to determine that it is safe to operate separately from distribution management and apply it to the
Vagrantcode> environment.However, I feel uneasy because I haven't seen any production operations in
When I participated in the PHP conference 2015 held recently, I had the impression that although PHP version issues were addressed, PHP installation method was not specifically addressed by users.
Therefore, I would like to ask you how PHP is installed in the production environment of PHP web development companies.
To sum up:
php-buildis the PHP installation tolerable for production?
I would appreciate it if you could let me know.php
If it's a production environment, the first choice is to use the package provided in the distribution.Development should also be targeted.
(And it would be nice if we could easily switch between multiple execution environments according to this production environment.)
If you build your own, you must consider both timely follow-up to security updates and version upgrade incompatibility (validation and response).The package provided by the distribution has been updated in the form of a security patch backport, which greatly reduces the burden on the latter.Of course, there is also a support issue.
It depends on how you operate it
There are two types of installation from the source or package perspective, but there are many variations of installation from the source.
It depends on the environment.
And these are not very well-formed questions because they are not correct and only have subjective answers. To get the right answers, check the help center and the questions in them to improve your questions
As for the direction of improvement in the question, the comment says, "Security updates may be slow for distribution packages," but if there is a requirement that such delays are not allowed and security updates must be applied quickly without exception, you can explain it.
Aren't there many other requirements that are only in your head?It would be a good question if you could provide specific requirements.
It's probably an illusion if you can't explain what you're being asked to do, but you think you can get the right answer from "miscellaneous opinions."The evaluation system of SO is of no help.Rather, consulting with a competent consultant is recommended.Most of their abilities are not knowledge of "correct answers themselves", but are specific to the ambiguous conditions that the customer cannot explain.
The title of the question may not be appropriate as it has been changed along the way, but since the original question was "What other installation methods are there?" we will then write down the information we have researched.
CentOS 6 provides the "other" PHP installation method:
Remi(Remi's RPM repository)
SCL (Software Collections for CentOS6)
It seems that you can use the .
It's not good to write the year as a title, so I'll write it here as of the beginning of 2016.
Remi has already been used on the web since around 2012, and since it contains a new version of PHP RPM, it seems that it has been used mainly by web designers until the beginning of 2016.
SCL was released by Redhat in 2013 for CentOS 6 of Redhat Software Collections, and I could not find any information in my observation that it was for a new version of PHP installation, but in March 2016, I was able to find out by offering "using SCL" as an alternative.see also: http://www.slideshare.net/atanaka7/zabbix30
Personally, I would like to hear the opinions of those who use these.
© 2022 OneMinuteCode. All rights reserved.