Commits on Jan 11, 2010
  1. Some small README fixes.

    committed Jan 11, 2010
  2. Ensure log rotation doesn't fail if nginx isn't running (i.e. on an i…

    …nstance not in the web role)
    committed Jan 11, 2010
Commits on Nov 2, 2009
Commits on Oct 29, 2009
  1. Set varnish's first_byte_timeout to 60 seconds (which is really long …

    …but it's not up to EC2 on Rails to enforce good performance within the Rails app).
    committed Oct 29, 2009
Commits on Oct 25, 2009
Commits on Oct 23, 2009
  1. Use varnish's round-robin director instead of random director to avoi…

    …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.
    committed Oct 23, 2009
  2. Fixed a typo.

    committed Oct 23, 2009
  3. Don't try to install rails each time setup is run because the gem com…

    …mand isn't very smart and it re-installs the gem even if it's already installed, which can be very slow.
    committed Oct 23, 2009
Commits on Oct 22, 2009
  1. Don't do init_backup every time db:create is run because it might be …

    …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.
    committed Oct 22, 2009
  2. Renamed gem to ec2onrails-experimental so it can be published without…

    … causing existing users to get it automatically when they upgrade.
    committed Oct 22, 2009
  3. Cleaned up the before/after hooks and cap tasks a bit:

    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
    committed Oct 22, 2009
  4. Merge branch 'experimental' into wip-jeweller

    * experimental:
      Restart god after changing RAILS_ENV because god stores the value of RAILS_ENV and uses it in notifications.
    committed Oct 22, 2009
  5. Restart god after changing RAILS_ENV because god stores the value of …

    …RAILS_ENV and uses it in notifications.
    committed Oct 22, 2009
  6. Moved files so that they're clearly related to the gem or to the serv…

    …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).
    committed Oct 22, 2009
  7. Merge branch 'experimental' into wip-jeweller

    * experimental:
      Removed unnecessary semicolon.
    committed Oct 22, 2009
Commits on Oct 20, 2009
  1. Converted to jeweler for gem building which allowed removal of gem ar…

    …tifacts (gemspec, Manifest, etc) and custom rake tasks to create those files.
    committed Oct 20, 2009
Commits on Oct 19, 2009
  1. Load the config file from /mnt/app/current/config/... instead of /etc…

    …/ec2onrails. Also renamed method.
    committed Oct 19, 2009
  2. Make sure rake gems:install doesn't get run when we're first deployin…

    …g the code before any server setup has been done.
    committed Oct 19, 2009
  3. Fixed some multi-instance bugs, especially the use of capture() which…

    … 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).
    committed Oct 19, 2009
  4. Reduce god's logging verbosity, log to god.log only (not syslog), and…

    … rotate and archive god.log daily.
    committed Oct 19, 2009
Commits on Sep 25, 2009
  1. Updated to Rails 2.3.4.

    committed Sep 25, 2009
  2. Don't do "reset master" after restoring, because this makes the backu…

    …p of the newly restored instance inconsistent until a full backup is done.
    Thanks to Frank O'Dwyer for pointing this out:
    committed Sep 25, 2009