Engine Yard Developer Center

Engine Yard Release Notes- July 2016

Engine Yard Stack Release Notes for July 28th, 2016

Minor: Engine Yard Gentoo 2016 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2016 environment.

Note: For clarity, since we now have 2 Gentoo stacks, we refer to this stack as the Engine Yard Gentoo 2016 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 2016 (stable-v5) stack regularly for the latest security and product updates. This week's updates:

  • Updated monit and Puma port mapping.
  • Fixed mytop configuration
  • Updated PHP support and Updated Versions of New Relic Items
  • Fixed /etc/descriptive_hostname and Updated hostname command
  • Fixed check_postgres path identification
  • Updated /tmp/composer_install.php for the composer installer
  • Updated God to the newest version so /mnt doesn't fill while the app doesn't start.
  • Updated nginx config to be fed from haproxy
  • Updated PostgreSQL config template to support PostgreSQL 9.5
  • Fixed check_postgres script
  • Initialized rudimentary offering of custom cookbook hook support: before-main after-main hooks
  • Updated custom recipes
  • Updated Ruby versions
  • Updated PostgreSQL
  • Added recipe for a quick chef run
  • Added ey-custom to ey-init metadata

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


Minor: Engine Yard Gentoo 2009 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 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:

stack_stable-v2.png

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:

  • Gave MySQL db_master server unique server-id values instead of 1

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


Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following 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:

stack_stable-v4.png

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

  • Installed rack 1.6.4 before installing Unicorn, to get around rack 2.0.1's dependency on Ruby 2.2.
  • Adjusted LC_COLLATE to POSIX to follow better standards and align with v5.
  • Improved support for long running MySQL startup.
  • Gave MySQL db_master server unique server-id values instead of 1

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


Engine Yard Stack Release Notes for July 12th, 2016

Minor: Engine Yard Gentoo 2009 stack upgrade

Action: You apply the following changes the next time you click the Upgrade button for your Engine Yard Gentoo 2009 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:

stack_stable-v2.png

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:

  • Fix MySQL & PostgreSQL alert types to prevent incorrect throttling.

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


Minor: Engine Yard Gentoo 12.11 stack upgrade

Action: You apply the following 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:

stack_stable-v4.png

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

  • Fix MySQL & PostgreSQL alert types to prevent incorrect throttling.

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


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk