Engine Yard Developer Center

AppCloud updates June 2011

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: Passenger 3 is now available with Beta support

June 29th, 2011

Phusion Passenger 3 is available with Beta support in AppCloud. (No sign-up required.)

Passenger 3 brings substantial performance improvements over Passenger 2.

 

 

Minor: The new Basic Cluster environment is now three medium servers

June 29th, 2011

For new environments, the default configuration is now a Basic Cluster of:

  • 2 medium application servers
  • 1 medium database server

Previously, the default environment was the Single Server configuration, and the Basic Cluster had only one application server (and one database server).

 

 

Fix: Changing the domain name for an environment

June 28th, 2011

Fixed an issue where changes to the Domain Name field were not saved. Domain names can now be changed in the Edit the Environment page.

 

 

Minor: A link to a sample application in GitHub is provided on the New Application page

June 24th, 2011

If you are new to AppCloud, test our sample repository and get the ToDo application up and running in your Engine Yard account.

 

Click Try our sample... to populate the Git Repository URI with the source code for the ToDo application. 

 

Try our sample ToDo application

 

 

Minor: Improved alert for out-of-date stacks

June 24th, 2011

When your Engine Yard stack is not the most current, you see this message under the environment name.

Stack update notice

 

Click !Update to update the stack. The message persists until the instance is running again and you refresh the browser page.

 

 

Minor: The Dashboard is now application-centric

June 21st, 2011

The Dashboard has moved from an environment-centric user interface to an application-centric user interface. For more information about this change, see We’re Getting Application-centric!

 

 

Minor: The default DB volume size is now 15GB

June 16th, 2011

The default size of the database volume has increased from 5GB to 15GB.

 

 

Minor: Mongrel is deprecated for new environments

June 16th, 2011

This does not affect environments currently running Mongrel.

If you need to create a new environment where Mongrel is the application server stack, please file a ticket with Engine Yard Support.

 

 

Fix: Automatic snapshot size

June 8th, 2011

Fixed an issue where the snapshot-size text field was not automatically updated when a specific snapshot was selected.

 

 

Fix: Environment update notification

June 8th, 2011

Fixed an issue where some environments were not marked as needing an update.

 

 

Fix: Rubygems 1.5.2

June 3rd, 2011

Patched a bug fix from June 1st that was causing problems.

 

 

Major: High memory XL VM’s available

June 3rd, 2011

You can now create high memory extra-large VM’s in your environment:

  • High memory XL (64 bit)

  • 6.5 ECU, 17.1GB RAM

  • 420GB of non-persistent storage

See www.engineyard.com/products/appcloud/pricing for pricing.

 

 

Minor: Environment variables for custom scripts

June 2nd, 2011

If you use custom scripts, your applications now have access to specific stack environment variables.

You can source /engineyard/bin/env.sh to access these variables: $EY_ENVIRONMENT_NAME, $EY_STACK, $EY_FRAMEWORK_ENV, $RAILS_ENV, $RACK_ENV, and $MERB_ENV.

 

 

Fix: HAProxy restart from single instance snapshot

June 2nd, 2011

Fixed an issue where HAProxy was failing to restart when creating a cluster from a single instance snapshot.

 

 

Fix: Rubygems 1.5.2 update

June 2nd, 2011

Upgrading to rubygems 1.5.2 was breaking Rails applications. This issue was fixed by adding version_requirements back into rubygems 1.5.2.

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