The updates described are either important (where you need to take action) or of interest (you might want to know about these changes but you don't need to do anything).
Early Access: Rubinius 2.0 support
October 31st, 2012
Action: Rubinius 2.0 is an optional Early Access release. No action required.
You can now use Rubinius 2.0 in both 1.8 and 1.9 modes. To do so, you’ll need to create a new environment or edit an existing environment and select either Rubinius 2.0 (ruby-1.8.7) or Rubinius 2.0 (ruby-1.9.3) in the Runtime drop-down. Rubinius 2.0 is part of our Early Access program.
Action: You can access the app instance size feature next time you add an instance.
Use the app instance size feature
The app instance size feature allows you to specify the size of the instance as well as the size of the volume. There is no restriction on instance or volume size, so you can use this feature to increase or decrease your cluster sizes as needed.
Action: You automatically apply these changes the next time you click the Upgrade button for your environment. If you use Nginx, there might be an extra step for you this week. SeeNginx version 1.2.3 support.
Updates Rubinius to use the 20121029 release. (Rubinius is in Early Access.)
Adds minor internal changes to support future functionality.
Action: If your environments use a custom Chef cookbook based on our ey-cloud-recipes repository, you will need to merge the current master branch into your fork or clone to take advantage of the following new custom Chef recipe:
Adds custom alerts thresholds via custom Chef recipe collectd. You can set custom alert levels for CPU load and root, /mnt, /data, /db volumes. For more information, see ey-cloud-recipes in GitHub.
Action: Contact Engine Yard Support if you upgraded to this week's stack and have experienced any upgrade issues. This week's stack upgrade was reverted due to an unforeseen incompatibility.
Updated Nginx version support from 1.0.15 to 1.2.3. (This is now reverted. Nginx 1.2.3 remains in Limited Access.)
Minor: New production configuration environment option
October 23rd, 2012
Action: You can access this feature next time you add an environment.
We recommend the production configuration environment for mid-to-high-scale applications that require high availability, a dedicated database with fail-over slave (replica) database, and horizontal scalability. The new production configuration includes:
3 Medium load-balanced application instances
Medium dedicated database instance
Medium slave database instance
new 15 GB persistent application snapshot
new 15 GB persistent database snapshot
With a new external IP address
1.7 GB RAM
350 GB of non-persistent storage
For more information, see the Engine Yard Cloud docs.
Minor: Engine Yard Cloud stack upgrade for Node.js
October 16th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your Node.js environment.
Adds respect for Node.js version set in package.json (latest versions supported: 0.6.21, 0.8.11).
Bumps default system Node.js version to 0.8.11.
Defines npm start, npm stop, npm restart, which allows you to customize the application lifecycle.
Removes alternate configurations when switching between TCP and HTTP proxying application server stacks.
Minor: Engine Yard Cloud stack upgrade
October 16th, 2012
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
Maintenance for future monitoring improvements; no current impact to users.
General Availability: Settable RubyGems version per environment
October 16th, 2012
Action: You can access this feature next time you add or edit an environment.
This feature allows you to choose the appropriate RubyGems version for each environment. For example, an environment using an older version of Rails would need a different RubyGems version than the default.
Major: Orchestra PHP Cloud supports PHP 5.4 and 5.3 stacks
October 3rd, 2012
Action: You can access this feature through the Orchestra PHP Cloud dashboard > Deploy an Application.
We are happy to announce the immediate availability of PHP 5.4.7 support for Orchestra PHP Cloud. With this upgrade, PHP 5.4 is the default stack for new apps. We will continue to support PHP 5.3, and you can optionally select this stack at deploy time.
Action: You automatically apply these changes the next time you click the Upgrade button for your environment. If you use OpenSSL directly, or have SSL certificates, there might be an extra step for you this week. See Security Update.
Fixes license issue when converting from the original New Relic integration to the New Relic add-on.
Security Update: OpenSSL (0.9.8x) now the default for Engine Yard Cloud
October 2nd, 2012
Action: We recommend you test this version of OpenSSL in your staging environment as soon as possible — before you click the Upgrade button for your environment.
Engine Yard is happy to provide for newer versions of OpenSSL (0.9.8x) as an improved security measure. OpenSSL is used by all your apps that handle encryption, from SSL certificates to certain encoding (like passwords in your app). OpenSSL is also used by many libraries and applications, such as Nginx for supporting HTTPS, and Ruby has a module for using OpenSSL in user apps.
We recommend that you upgrade your environments to this updated version, beginning with staging. Contact Engine Yard Support to schedule a time to stage this upgrade.
Important: This week's release makes 0.9.8x the new default; it will be used once you upgrade your environment.
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.