…nstance not in the web role)
…but it's not up to EC2 on Rails to enforce good performance within the Rails app).
…d getting 503 errors when some (but not all) back-ends are down. (The random director doesn't necessarily try all back-ends, even if retries is set >= than the number of back-ends.) BTW this is only for balancing between back-end nginx servers and there's no problem doing round-robin here, the web servers themselves are still using Passenger's global queueing to balance between the Rails back-ends so there is no issue with one slow request holding up all the others.
…mand isn't very smart and it re-installs the gem even if it's already installed, which can be very slow.
…slow if there is a large database that already exists. This matters especially after changing the running instances (e.g. adding more app servers) because when you do ec2onrails:setup it will run db:create (harmless) on the existing db. Added a TODO in create_database to do the backup then, but first we need to check for the existence of the db and exit if it exists.
…sion of the gem.
… causing existing users to get it automatically when they upgrade.
1. Stop using deploy:cold 2. Removed the db:optimize hook (if it should be run on setup then it should be part of the ec2onrails:setup task, but it's untested right now and I'm reluctant to add it to the default setup until someone can confirm that it works) 3. run ec2onrails:db:init_backup after creating the db 4. removed the add_gem_sources task, gem dependencies in recent versions of Rails can specify a source 5. purge the proxy cache after redeploying
…RAILS_ENV and uses it in notifications.
…er. We can do this now that we're no longer using GitHub to build the gem (GitHub's gem builder expected the gem files to be at the root).
…tifacts (gemspec, Manifest, etc) and custom rake tasks to create those files.
…/ec2onrails. Also renamed method.
…g the code before any server setup has been done.
… only executes it's command on one server (it should only be used to get some info from the server, not for things that should have side effects).
… rotate and archive god.log daily.
…p of the newly restored instance inconsistent until a full backup is done. Thanks to Frank O'Dwyer for pointing this out: http://groups.google.com/group/ec2-on-rails-discuss/browse_thread/thread/e2386df3d329b9a5