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).
Major: Engine Yard Cloud adds 64-bit Normal/Small & High-CPU/Medium instances
April 25th, 2012
Engine Yard Cloud now supports the new 64-bit Normal/Small and High-CPU/Medium instance types.
Important: If you are booting from a snapshot, be sure the architecture matches. For example, a 32-bit snapshot should be applied to a 32-bit small or 32-bit medium instance.
Action: You choose the 32-bit or 64-bit operating system when using these 2 instance types.
Minor: Engine Yard stack upgrade
April 12th, 2012
The following changes have been made to the Engine Yard stack:
- Fixes issue that installed Nginx and an application server in utility instances.
- Sets default language in instances to en_US.utf8.
- Fixes issue with snapshot configuration.
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
Major: Ruby 1.9.3 is now available for general access (GA)
April 5th, 2012
Ruby 1.9.3 has been released as GA and the default runtime when creating a new application.
Action: To learn more, see Ruby 1.8.7 and REE End of Life.
Major: PostgreSQL 9.1.3 is now available for general access (GA)
April 5th, 2012
PostgreSQL 9.1.3 is available on Engine Yard Cloud and Engine Yard Managed as a fully supported GA release.
Action: To learn more, see Getting more out of Postgres 9.1 on Engine Yard.
Minor: Engine Yard stack upgrade
April 3rd, 2012
The following changes have been made to the Engine Yard stack:
- Upgrades Ruby 1.9.3 version to patch 125.
- Upgrades Rubygems version to 1.8.17.
- MySQL snapshots no longer get stuck when more than one are requested close together.
- Removes X-Request-Start header from the Nginx configuration to follow New Relic recommendations.
- Fixes problems with stuck deployments on the Trinidad application server stack.
- Upgrades PostgreSQL server to version 9.1.3. Note: this change becomes effective only after an instance restart.
- Provides a way to add customizations to the pg_hba.conf file without causing PostgreSQL to restart.
- PostgreSQL gem now works with PostgreSQL 9.0 and above.
Action: You automatically apply these changes the next time you click the Upgrade button for your environment.
Priyanka Bhotika
Comments