Engine Yard Release Updates January 2014

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

Minor: Engine Yard Gentoo 2009 stack upgrade

January 30th, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" stack. You can access it by using the Stack select field in the Environment UI:

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

• Adds RAILS_ENV, RACK_ENV and PATH to environment for user-owned cron jobs.
• For Ruby applications only -- Fixes incorrect HTTP status code when maintenance page is displayed (code 503 is now returned instead of 200).

Minor: Engine Yard Gentoo 12.11 stack upgrade

January 30th, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 12.11" stack. You can access it by using the Stack select field in the Environment UI:

 

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

• Adds RAILS_ENV, RACK_ENV and PATH to environment for user-owned cron jobs.
• For Ruby applications only -- Fixes incorrect HTTP status code when maintenance page is displayed (code 503 is now returned instead of 200).
• Fixes issue where New Relic dynamic library goes missing after adding or removing instances.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

General Availability: Access Control

January 29th, 2014

Action: You can invite other team members and assign them the necessary access today!

We are very happy to announce the General Availability (GA) of the access control feature on Engine Yard. You can now enable multiple members of a team to access multiple environments and assign individual access privileges for those team members.

For full details of the feature, see Use Collaboration and Access Control on Engine Yard.

Minor: Engine Yard Gentoo 2009 stack upgrade

January 23rd, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" stack. You can access it by using the Stack select field in the Environment UI:

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

• Upgrades to PostgreSQL 9.2 & 9.3 to address corruption and VACUUM bugs.
• Fix to remove an unnecessary password warning on MySQL 5.6.

Minor: Engine Yard Gentoo 12.11 stack upgrade

January 23rd, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 12.11" stack. You can access it by using the Stack select field in the Environment UI:

 

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

• Upgrades to PostgreSQL 9.2 & 9.3 to address corruption and VACUUM bugs.
• Upgrades installed version of check_postgres.pl for proper support of newer PostgreSQL versions.
• Tuned sysctl for better performance under load.
• Fix to remove an unnecessary password warning on MySQL 5.6.
• Upgrades to PHP to address CVE-2013-6420.
• Fixes missing maintenance page for PHP apps.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

Minor: Engine Yard Gentoo 2009 stack upgrade

January 9th, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 2009" stack. You can access it by using the Stack select field in the Environment UI:

It's best practice to upgrade your Engine Yard Gentoo 2009 (stable-v2) stack regularly for the latest security and product updates. This week's updates:

• Fixes security issues related to OpenSSL.

Minor: Engine Yard Gentoo 12.11 stack upgrade

January 9th, 2014

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

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the "Engine Yard Gentoo 12.11" stack. You can access it by using the Stack select field in the Environment UI:

 

It's best practice to upgrade your Engine Yard Gentoo 12.11 (stable-v4) stack regularly for the latest security and product updates. This week's updates:

• Adds recipe to create a swapfile on instance types that do not have a swap partition.

For more information on Engine Yard Gentoo 12.11, see the Engine Yard Gentoo 12.11 docs.

---

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