Engine Yard Developer Center

Engine Yard Release Notes- October 2017

 

Engine Yard Stack Release Notes for October 31st, 2017

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: stable-v5-3.0.33

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:

  • Adds support for timezone controls to PostgreSQL
  • Adds support for Postgres versions 9.5.7 and 9.6.3
  • Adds cookbooks support for RDS databases and users (available for Beta)
  • Adds support for logical backups of RDS databases 
  • Adds automatic database engine detection based on the environment DNA
  • Updates the elasticsearch recipe to support multiple utility instances named "elasticsearch" instead of using elasticsearch_1, elasticsearch_2, etc.
  • Fixes security exceptions when starting Solr
  • Adjusts the DelayedJob default monit timeout so that it is longer than the dj script timeout
  • Adds HTTP/2 support
    NOTE: You need to upgrade Nginx to version 1.12.1 or later to use HTTP2. Please open a Support ticket if you need assistance with this

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

 


 

Engine Yard Stack Release Notes for October 9th, 2017

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: stable-v5-3.0.32

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:

NOTE: Our chef recipes do not restart Passenger, as doing this in a chef run can result in a simultaneous restart across all application instances, causing downtime. However, a restart is needed to run the newer Passenger version. To restart Passenger, please run "sudo monit restart passenger_APPNAME_8000" on all app instances. We recommend doing this on a staggered basis to avoid downtime.

For more information on Engine Yard Gentoo 2016, see the Engine Yard Gentoo 2016 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