Engine Yard Release Updates December 2012

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).

Hotfix: Riak configuration update

December 21st, 2012

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

We changed a couple minor configuration items that were causing downstream issues for some customers.

• Fixes configuration values for LevelDB backend names for Riak clusters.

This affects only those customers participating in the Limited Access phase of the Riak intro.

Minor: Engine Yard Cloud stack upgrade

December 18th, 2012

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

• Adds application/json mime type to Nginx mime.types.
• Removes HTML text from the default nginx.conf file.
• Rotates Redis log.
• Deprecates New Relic seed and token.
• Fixes eybackup issue with Chef 10 (Limited Access release).
• Fixes multi-backend configuration in Riak (Limited Access release).

Minor: Engine Yard Gem 2.0.10

December 17th, 2012

Action: You can try the 2.0 gem in a staging environment before you deploy to production.

The Engine Yard blog provides the information you need to know about this 2.0 gem.

This minor release includes:

• Adds command line option -q (or --quiet) to mute non-essential CLI output for most commands.
• Supports new ey.yml option during deploy to control which roles pre-compile assets.
• Follows YAML Array syntax (using :app, :app_master, :solo, :util) or :all.
• Syntax: asset_roles: :all (default is to exclude :util and include :app, :app_master, and :solo)
• During deploy, adds RAILS_GROUPS=assets to rake assets:precompile to improve asset compilation performance.
• Records exceptions raised during deploy into the deploy log when possible.
• Fixes a bug where permissions problems may cause integrate action to fail.
• Fixes an issue where "maintenance page still up" notice would stay on Cloud dashboard too long. Downgrades message severity.

• Garbage collect git at the end of each deploy.

  Note: The first garbage collection might take a while; subsequent garbage collection will be faster and will reduce extra disk usage.

You can download the gem here. For more information, see the GitHub change log and the readme.

Minor: Engine Yard Cloud stack upgrade

December 11th, 2012

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

• Updates load_foreign_postgres_db script to specify user and stop connections before dropping database.
• Improves instance add times by approximately 20 percent (by deferring eix-sync, which builds the package manager index, to after boot).

Minor: Engine Yard Cloud stack upgrade

December 4th, 2012

Action: You automatically apply these changes the next time you click the Upgrade button for your environment.

• Maintenance to support future monitoring enhancements.

If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.