什么错在同一Apache服务器上运行PHP和Ruby？ [英] Anything wrong with running PHP and Ruby on the same Apache server?
问题描述
我们正在试图找出我们可用的服务器，这是为数不多之间分发我们的应用程序的最佳方式。
We are trying to figure out the best way to distribute our applications among our available servers, which are few in number.
假设足够的内存和CPU处理能力，是否有我们不应该运行任何理由 mod_php的和 mod_rails （客）在同一Apache服务器内？他们会不会发生冲突或冲突不知何故？
Assuming adequate RAM and CPU power, is there any reason we shouldn't run mod_php and mod_rails (Passenger) within the same Apache server? Would they clash or conflict somehow?
推荐答案
有与使用同一个Apache服务器上mod_php，并且和mod_rails风险不大。
There is little risk with running mod_php and mod_rails on the same Apache server.
在实际上，乘客也不会，如果它出现故障，因此实际上是Apache和mod_php，并且使用一个不错的选择影响了Apache。从客运结构概述：
In fact, Passenger won't affect Apache if it goes down so it is actually a good choice to use with Apache and mod_php. From the Passenger Architectural Overview:
应当指出的是，红宝石上
Rails应用程序在不运行
相同的地址空间的Apache。这个
从其他客运区别
应用服务器内的Web服务器
软件如mod_php，并且和的mod_perl
mod_ruby。如果Rails应用程序
崩溃或泄漏内存，就会产生
在Apache没有影响。事实上，
稳定是我们的最高目标之一。
乘客精心设计
实现这样Apache不应该
因为乘客的崩溃。
It should be noted that the Ruby on Rails application does not run in the same address space as Apache. This differentiates Passenger from other application-server-inside-web-server software such as mod_php, mod_perl and mod_ruby. If the Rails application crashes or leak memory, it will have no effect on Apache. In fact, stability is one of our highest goals. Passenger is carefully designed and implemented so that Apache shouldn't crash because of Passenger.
这篇关于什么错在同一Apache服务器上运行PHP和Ruby？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
