January 2011
2 posts
AppCloud v457 Deployed
ENHANCEMENTS:  Ruby 1.9.2 users will find the database.yml generated with the mysql2 driver ENHANCEMENTS: Unicorn script issue where you saw ‘command not found’ is corrected and should no longer be displayed.
Jan 19th
AppCloud v439 Deployed
ENHANCEMENTS:  The Following updates have been made to the Unicorn control script. Control script has  the path to include /data/<appname>/current/ey_bundler_binstubs which removed an OR condition which was confusing. No longer tries to reload unicorn if it takes an excess of 30 seconds. Changed the sleep periods started with a 30 second period if your application deploys in that short...
Jan 4th
2 notes
December 2010
7 posts
S3 & EBS Volumes Are Slow
Though Amazon has not acknowledged it today, we are seeing many reports from our customers that S3 and EBS volumes are performing very slow today. This may affect your application’s performance.
Dec 17th
Deploy Issues Have Been Fixed
We’ve tracked down the issue causing deploys to fail and fixed it.
Dec 17th
Deploy problems still unresolved
We continue to experience deploy problems. We continue to work on the fix. We apologize for the inconveniences.
Dec 17th
1 note
Deploy issue should be fixed
Deploy issue should now be resolved. If you continue to experience problems, please contact us.
Dec 17th
Dashboard issues may cause problems deploying
Currently we are experiencing issues with our Dashboard. We are actively working to resolve them, and you are able to access it but there may be some problems deploying.
Dec 16th
Failover Monitoring Problem
If a chef run occurred on any of your instances between November 29th and late December 1st, then the failover monitoring is most likely in a broken state. This is due to a bug that was introduced in version 0.2.5 of the Excon gem that’s used in failover monitoring. The gem was updated quickly and the fixed version is now being used, but you have to perform a full chef run to get the fix (a...
Dec 2nd
AppCloud v387 Deployed
BUGFIX: Unicorn failing to reload for non-bundler users ENHANCEMENT: Unicorn now tries to bundle exec unicorn/unicorn_rails by default and if that is not available uses the system unicorn gem to run.  Additionally tries to resolve failed deploys in a reliable manner.  NOTE: If you use env.custom to enable a bundle exec unicorn you should revert those customizations as they are no longer...
Dec 1st
November 2010
2 posts
AppCloud v371 Deployed
BUGFIX: the dashboard is now firesheep-proof (SSL on all pages + Secure Connection-only cookies).
Nov 10th
AppCloud v358 Deployed
BUGFIX: Fixed a bug where Unicorn was being restarted on deploy rather than reloaded.
Nov 3rd
October 2010
11 posts
AppCloud v356 Deployed
BUGFIX: Snapshots weren’t completing properly in some cases due to failed EC2 requests. BUGFIX: Under certain conditions, database backups were deleting the most recent rather than oldest backup.
Oct 29th
AppCloud v350 Deployed
CHANGE: Improved UI of Applications area. CHANGE: Improved look for gem and unix package dependency pages. FEATURE: Improved SSH key management. You can now control which environments a key is installed to in one centralized location per key. Just go to the SSH keys area in the dashboard and click on the link for the SSH key (the name of the key). You’ll then be able to check off which...
Oct 29th
AppCloud v352 Deployed
BUGFIX: Fixed a bug that was keeping you from adding utility instances to clusters in the Boot Instances form.
Oct 29th
AppCloud v347 Deployed
BUGFIX: Clicking “ship it” without a branch specified now results in an error. BUGFIX: SSL certificate validation errors now show up properly.
Oct 29th
AppCloud v346 Deployed
BUGFIX: When enabling, changing or disabling NewRelic, the user is now told to rebuild their environment. BUGFIX: Fixed a bug where creating a new environment was behaving like instances were already running so you weren’t able to edit some options. BUGFIX: Validations errors now show up properly when creating a new environment.
Oct 29th
AppCloud v345 Deployed
CHANGE: You can now attempt to change the stack an environment is using (Passenger/Mongrel/Unicorn) without having to terminate and spin up your instances again. A rebuild is required though (and you may end up needing to make some manual tweaks if you do this).
Oct 29th
AppCloud v344 Deployed
BUGFIX: CLI deploy integration step that’s run when an instance is being added to a cluster no longer mistakenly runs when using the Legacy Deploy method for an environment.
Oct 29th
AppCloud v343 Deployed
BUGFIX: Deploy lightbox now has a scrollbar when an environment has lots of applications.
Oct 29th
AppCloud v338 Deployed
BUGFIX: Fixed a javascript issue on the application gem dependency page when performing searches. CHANGE: Renaming environments is temporarily disabled until another issue regarding that can be resolved. CHANGE: The page where you add applications to an environment now sorts applications by name.
Oct 12th
AppCloud v337 Deployed
BUGFIX: Nightly snapshots script was incorrectly marking instances as red if it had to retry initiating the snapshot. BUGFIX: If instances fail to provision the “Acknowledge” link shows up faster. CHANGE: Minor UI enhancements based on user feedback (e.g., selected tabs for environments have an active state image now). CHANGE: REE is no longer marked as “beta”.
Oct 8th
4 notes
AppCloud v335 Deployed
BUGFIX: Fixed some display issues in the database backup listing where backups that existed weren’t displayed like they should have been. BUGFIX: The newrelic.yml file is now added to utility instances for environments using the integrated NewRelic feature.
Oct 7th
AppCloud v327 Deployed
CHANGE: Worker counts were adjusted with Mongrel and Passenger and Unicorn.  
Oct 1st
September 2010
7 posts
AppCloud v325 Deployed
BUGFIX: Fixed a UI bug where you weren’t able to add applications to an environment that didn’t already have applications added.
Sep 28th
CLI v1.3.1 Released
BUGFIX: Fixed a bug that was breaking deploys under Ruby 1.9.2.
Sep 21st
CLI v1.3.0 Released
FEATURE: You can now pass additional options to your deploy hooks from the command line (e.g., —extra-deploy-hook-options key1:value1 key2:value2) BUGFIX: `ey rollback` now symlinks the correct release into place (it had been symlinking the same release it was rolling back)
Sep 14th
AppCloud v312 Deployed
CHANGE: UI enhancements made to the Edit Environment page.
Sep 14th
AppCloud v304 Deployed
CHANGE: New environments now default to the CLI deployment method.
Sep 4th
Cancellation Emails Sent for Dormant Accounts
Some cancellation emails were mistakenly sent for many inaccessible accounts as part of a billing process. If you received an email, it’s likely that you had a dormant account laying around that was never accepted. Your normal account should not be affected. If your normal account was affected, just log in and accept the terms of service and choose your support plan again. You may be asked...
Sep 2nd
August 2010
17 posts
CLI v1.2.4 Released
FEATURE: Migration command is now bundler-aware; you don’t need to specify ’bundle exec rake db:migrate’ to get your bundled gems loaded. Note that this is accomplished using bundler 1.0’s binstubs, so bundler 0.9 users don’t get this. CHANGE: Bundler 1.0.0 is now the default 1.0-series bundler. This should make Rails 3 apps deployable.
Aug 31st
CLI v1.2.2 Released
BUGFIX: Multiple apps in AppCloud with the same git url are now handled correctly. If there is ambiguity, we ask you to specify the app to deploy.
Aug 31st
AppCloud v294 Deployed
BUGFIX: Fixed an issue with the Mongrel monitrc file that was introduced in v293 where some environment variables weren’t being set properly.
Aug 26th
CLI v1.2.1 Released
BUGFIX: Deploy hooks are now aware if migrations have run; use the #migrate? method. BUGFIX: Should now work properly with Ruby 1.9.2. CHANGE: Default migration command is now ‘rake db:migrate —trace’ for easier debugging. CHANGE: Use latest bundler release candidate for compatibility with latest Rails release candidate.
Aug 26th
AppCloud v293 Deployed
CHANGE: Mongrel and Passenger now use control scripts in /engineyard/bin for starting/stopping/etc.
Aug 26th
AppCloud v291 Deployed
BUGFIX: The unicorn control script wasn’t restarting unicorn properly due to a bug in how it checked the pid. That check has been removed until the bug can be worked out. So, unicorn should have less trouble restarting properly now.
Aug 26th
AppCloud v290 Deployed
BUGFIX: /engineyard/bin/thinking_sphinx_searchd now works better with bundler. BUGFIX: /engineyard/bin/resque updated with various bugfixes and enhancements. BUGFIX: Unicorn runscripts now change the working directory to the app directory before executing commands to work slightly better with bundler. Also, RAILS_ENV, RACK_ENV, and MERB_ENV are now exported like they should have been. BUGFIX:...
Aug 24th
CLI v1.2.0 Released
CHANGE: Some backend changes were made warranting a version bump, but nothing that should be noticeable from a user standpoint.
Aug 18th
CLI v1.1.3 Released
BUGFIX: Avoid unnecessary uses of sudo. BUGFIX: Don’t start unicorns with sudo. BUGFIX: Don’t fail if no Gemfile.lock file exists when using Bundler (note, that you *should* have a Gemfile.lock file) Note that if you’re running unicorns that are root, you’ll have to manually stop them with sudo; this version can’t restart them. Newly-created instances will be...
Aug 17th
CLI v1.1.2 Released
BUGFIX: Git submodules should be supported properly now.
Aug 12th
AppCloud v279 Deployed
BUGFIX: Attempting to boot a new environment if that environment had utility snapshots would fail. This is now fixed. On a related note, we realize there have been a lot of issues involving utility snapshots recently. We’re working on hammering all of those bugs out and making sure regression tests are in place to avoid these issues going forward.
Aug 11th
AppCloud v278 Deployed!
BUGFIX: When booting an environment from scratch, the snapshot that was selected for utility instances wasn’t used. Instead you got a new volume. This should now be fixed (this is separate from a previous bug where a utility instance added to an existing environment wasn’t using the selected snapshot).
Aug 11th
AppCloud v275 Deployed!
BUGFIX: Utility instances were always being booted with a new volume regardless of the snapshot that was selected. This is now fixed.
Aug 7th
AppCloud v272 Deployed!
CHANGE: Extras page in the dashboard was removed. CHANGE: Adding an application slave instance now uses the latest app master snapshot rather than taking a new snapshot when you add it. CHANGE: Instances page removed from the dashboard (link was under Server Management on the left). FEATURE: Ruby Enterprise Edition (REE) is now available as a Ruby option for all customers in a beta capacity.
Aug 5th
AppCloud v271 Deployed!
BUGFIX: Database backups are now sorted properly. FEATURE: framework_env displayed next to environment name in dashboard now. Note that this deploy actually occurred yesterday.
Aug 5th
AppCloud v270 Deployed!
BUGFIX: Git http urls are now validated (i.e., you see an error when you try to use an http url rather than a git url). BUGFIX: Fixed a typo in monit scripts for Unicorn stacks.
Aug 4th
AppCloud v269 Deployed!
BUGFIX: Fixes snapshot ordering in the dropdown menu. They now appear in reverse chronological order as expected.
Aug 3rd
July 2010
37 posts
AppCloud v261 Deployed!
BUGFIX: Timestamp for snapshots in the Create Instance snapshot dropdown is now correct again.
Jul 29th
AppCloud v260 Deployed!
FEATURE: Snapshot status now updates in the dashboard (and there was much rejoicing).
Jul 29th
AppCloud v258 Deployed!
BUGFIX: Fix eybackup download failure when /mnt/tmp does not exist. BUGFIX: Fix eybackup to use single transaction dumps when no MyISAM tables exist.
Jul 29th
AppCloud v255 Deployed!
BUGFIX: Use /etc/portage/package.use/local file instead of /etc/portage/package.use.
Jul 28th