Engine Yard Home

  • Sales 866-518-YARD

Engine Yard Platform

To ensure your satisfaction, we are continually working on the Engine Yard stack.

The Engine Yard Technology Stack is a fully-curated Ruby on Rails web application framework stack, designed and optimized for business-critical Ruby on Rails application development. Each individual component within the stack has been customized and optimized over the course of 1,000s of developer hours by engineers at Engine Yard, which includes leading Ruby on Rails contributors, expert cluster engineers and seasoned DBAs for web server performance, database efficiency and long-term scalability. We meticulously test and fully integrate each new component and component update to provide reliability, security and compatibility within the stack.

As a result of all the work we do, you can confidently deploy and manage your application with any Engine Yard cloud product. Read about the many benefits of using our Platform-as-a-Service.

This version is correct as of August 1, 2010.

Subscribe to updates

Are you an Engine Yard customer?

If you have suggestions about our products and services, feel free to send us your suggestions via a support ticket at http://support.cloud.engineyard.com. We look forward to hearing from you.

Category Component Engine Yard Recommends Engine Yard AppCloud Support xCloud Support Versions to avoid
and other comments
Ruby Interpreters MRI 1.8.7.p174 1.8.7.p174
1.8.6.p287 (patched) 		1.8.7.p174
1.8.6.p383 		1.8.5 and below, 1.8.6.p369 and below, 1.8.7.p171 and below, (multiple vulnerabilities)
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=ruby
1.9.1 is not supported although we anticipate offering experimental support for Ruby 1.9.2 when it ships
JRuby/JVM — — 1.3.13
JDK 1.6u16 		JRuby support is in beta3 status for Engine Yard AppCloud
REE — 2010.023 2010.023 REE Support in beta3 status
Frameworks Rails 2.3.8 2.3.8
2.3.5
2.3.4
2.3.3
2.3.2
2.2.2
2.1.2
2.0.1→52
1.2.0→52
1.1.0→62 		3.0.0.beta1
2.3.8
2.3.5
2.3.4
2.3.3
2.3.2
2.2.2
2.1.2
2.0.1→52
1.2.0→52
1.1.0→62 		Rails 3.0.0.beta Support is in experimental status for xCloud customers only.
2.3.8 does not work with mongrel.
2.3.3 and below must apply a patch for a cross-site scripting vulnerability
2.3.2 and below (multiple vulnerabilities)
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rails
http://groups.google.com/group/rubyonrails-security/browse_thread/thread/20e17a978d2ccbd3?hl=en&nbsp
Merb 1.0.12 1.0.12 1.0.12 Avoid 1.0.11 and below (vulnerability in json_pure)
Engine Yard recommends latest release of 1.0 line with latest bug fixes
Web/App nginx 0.6.35-r25
(patched) 		0.6.35-r25
(patched) 		0.6.35-r25
0.5.37
(patched)
0.7.65-r23 		0.6.38 and below must apply several security patches
0.7.65-r2 support is in beta3 status for xCloud
mongrel 1.1.5.1 1.1.5.1 1.1.5.1 1.1.3 and below (multiple vulnerabilities)
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-6612
unicorn 1.0.1 1.0.1 1.0.1
haproxy 1.4.2 1.4.2 1.4.2
nginx/psgr 0.6.35/2.2.8 0.6.35/2.2.8 0.6.35/2.2.8 Passenger 2.2.3 (memory leak issues)
nginx must apply several security patches
rack 1.0.1 1.0.1
0.9.12 		1.0.x All versions prior to 0.9.1 (vulnerability)
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/324389
Databases MySQL 5.0.77 5.0.51 5.0.77
5.0.51
5.0.45
5.1.383 		5.1 before 5.1.34 (multiple vulnerabilities)
5.0 before 5.0.45 (multiple vulnerabilities)
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mysql
5.1 beta support on dedicated databases on xCloud
Postgres 8.4.1 — 8.2.14
8.3.8
8.4.1 		All 8.2.x versions prior to 8.2.13, all 8.3.x versions prior to 8.3.7
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=postgresql
MongoDB 1.2.43 — 1.2.43 Supported only on dedicated databases on xCloud.
Caches & Stores memcached 1.4.1 1.4.1
1.2.6 		1.4.1
1.2.6 		 
Tokyo1
..Cabinet
..Tyrant
..Dystopia 		 
1.4.33
1.1.34
0.9.13 		   
1.4.x
1.1.x
0.9.x 		Must be properly tuned for large datasets
Redis 1.2.63 1.2.63 1.2.63 Recommend against the use of very large data sets with Redis 1.0
OS Gentoo EY Portage EY Portage EY Portage  
Background Job Processor delayed_job 2.0.3 2.0.3 2.0.3 We recommend use of the latest versions
We recommend against use of BackgroundRB
BackgroundJob 1.0.1 1.0.1 1.0.1
resque — 1.5.01 1.5.01
Search Sphinx
(+Thinking Sphinx) 		0.9.9 — 0.9.9  
AVOID awstats N/A — — awstats is no longer supported within any Engine Yard environment. We recommend use of Google Analytics in its stead.
Ferret N/A — — Engine Yard recommends against use of any version of Ferret
Juggernaut N/A — — Engine Yard recommends against the use of any version of Juggernaut.
WordPress N/A — — Engine Yard recommends use of a specialist WordPress hosting service for WordPress installations
1 These components are designated "experimental" for support purposes and are there for you to test and experiment with, but Engine Yard does not expect you to use these components in a production environment. If you encounter issues with an "experimental component", Engine Yard is interested in any feedback you are willing to share. Please submit a support request through the normal access methods. Engine Yard cannot, however, commit to troubleshoot, provide workarounds or provide fixes for these "experimental components", and there is no SLA offered when experimental components are used in production. Experimental components are listed for the purposes of displaying what components are in the pipeline toward fully supported status. But there is no guarantee that these components will, in fact, be supported at any future date—in many cases, our evaluation of experimental components result in a decision not to support the component. 2 These version numbers are not covered by Engine Yard Support, although these versions may be installable from the user interface. 3 Engine Yard offers Beta Support for components not currently covered under Engine Yard's standard support services but included on a beta testing basis in the Engine Yard Technology stack. Beta Support enables customers to submit support requests on how to install and configure the component according to its native documentation. For components covered under Beta Support, Engine Yard will also provide troubleshooting support on a 'best effort' basis. Because we don't expect components covered by Beta Support to be implemented in a production environment, our response to support tickets may take longer than for components covered by our standard support services. Engine Yard may forward any bug information to the developer community as appropriate. Depending on the timing and severity of an issue, bugs may or may not be corrected before a later version of the component is released and included in the Engine Yard Technology Stack. This listing is not exhaustive, but covers the essential components of the Engine Yard Stack. We will install other commonly used components, such as solr, upon request but they will not be covered by Engine Yard support plans, nor does the Engine Yard SLA apply when these components are used.