mod_ruby
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Mod ruby" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Mod ruby|concern=Content is very domain-specific. It is not notable.}} ~~~~ Timestamp: 20150126175236 17:52, 26 January 2015 (UTC) Administrators: delete |
![]() | The topic of this article may not meet Wikipedia's notability guidelines for products and services. (August 2014) |
This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. (August 2014) |
mod_ruby | |
---|---|
Stable release | 1.3.0
/ November 8, 2008 |
Repository | |
Website | modruby![]() |
mod_ruby is a module that embeds the Ruby interpreter into the Apache web server to allow Ruby code to execute natively, faster than other CGI methods. Its drawback is that the characteristic sharing of classes among Apache processes is not safe for multiple applications[1] (e.g., multiple Ruby on Rails applications running simultaneously).
There is also the similar mod_mruby for mruby, a lightweight Ruby implementation.
As of at least 2015, the project seems to no longer be under active development.
See also
Notes
- ^ [dead link]mod_ruby Wiki, explaining the security problem of mod_ruby.
External links