@@ -1,6 +1,7 @@ -== 0.9.9.1 2009-01-25 +== 0.9.9.1 2009-01-27 -* ami-xx (32-bit) and ami-xx (64-bit) +* US AMI's: ami-5394733a (32-bit) and ami-5594733c (64-bit) +* EU AMI's: ami-761c3402 (32-bit) and ami-701c3404 (64-bit) * This is just a bug fix release for 0.9.9, it doesn't include the (huge) changes from the github master branch (EBS, etc.) * Updated to Ubuntu 8.04.2 LTS (https://wiki.ubuntu.com/HardyReleaseNotes/ChangeSummary/8.04.2) * Built with ec2ubuntu build script version 125 (http://alestic.com) @@ -10,7 +11,10 @@ * Updated rails gems (2.2.2, 2.1.2, 2.0.5, 1.2.6) * Updated build script to work with git repo * Removed PHP packages -* Bug fix: Increased the time to wait for mongrel processes to restart before re-enabling monitoring (to avoid warning messages from monit) +* Apache now sets the X_FORWARDED_PROTO header to "https" for SSL requests so request.ssl? will work +* Apache now removes the Client-IP HTTP header if it's set to prevent Rails from raising an erroneous "IP spoofing attack?!" exception +* Bug fix: now sets the db_primary hostname alias on all hosts, not just those in the app role +* Bug fix: increased the time to wait for mongrel processes to restart before re-enabling monitoring (to avoid warning messages from monit) * Bug fix: fixed server:install_packages capistrano task (now updates package list) * Bug fix: now automatically handles an Elastic IP being associated or disassociated (automatically checks every 15 mins to see if the hostname has been changed and resets anything that depends on the hostname) * Bug fix: doesn't try to rotate apache logs if they don't exist. This previously resulted in a warning email. gem/History.txt @@ -37,8 +37,6 @@ Capistrano::Configuration.instance.load do cfg = ec2onrails_config set :ec2onrails_version, Ec2onrails::VERSION::STRING - set :image_id_32_bit, Ec2onrails::VERSION::AMI_ID_32_BIT - set :image_id_64_bit, Ec2onrails::VERSION::AMI_ID_64_BIT set :deploy_to, "/mnt/app" set :use_sudo, false set :user, "app" @@ -93,8 +91,10 @@ Capistrano::Configuration.instance.load do EC2 on Rails. DESC task :ami_ids do - puts "32-bit server image for EC2 on Rails #{ec2onrails_version}: #{image_id_32_bit}" - puts "64-bit server image for EC2 on Rails #{ec2onrails_version}: #{image_id_64_bit}" + puts "32-bit server image (US location) for EC2 on Rails #{ec2onrails_version}: #{Ec2onrails::VERSION::AMI_ID_32_BIT_US}" + puts "64-bit server image (US location) for EC2 on Rails #{ec2onrails_version}: #{Ec2onrails::VERSION::AMI_ID_64_BIT_US}" + puts "32-bit server image (EU location) for EC2 on Rails #{ec2onrails_version}: #{Ec2onrails::VERSION::AMI_ID_32_BIT_EU}" + puts "64-bit server image (EU location) for EC2 on Rails #{ec2onrails_version}: #{Ec2onrails::VERSION::AMI_ID_64_BIT_EU}" end desc <<-DESC @@ -129,6 +129,7 @@ Capistrano::Configuration.instance.load do Prepare a newly-started instance for a cold deploy. DESC task :setup, :roles => all_admin_role_names do + server.update_hostname server.set_admin_mail_forward_address server.set_timezone server.install_packages @@ -307,6 +308,16 @@ Capistrano::Configuration.instance.load do rails_env = fetch(:rails_env, "production") sudo "/usr/local/ec2onrails/bin/set_rails_env #{rails_env}" end + + desc <<-DESC + Tell the server that an elastic IP has been assigned so it can + reconfigure the things that depend on knowing it's hostname. + (It checks every 15 minutes anyway so this is not strictly + necessary.) + DESC + task :update_hostname, :roles => all_admin_role_names do + sudo "/usr/local/ec2onrails/bin/update_hostname" + end desc <<-DESC Upgrade to the newest versions of all Ubuntu packages. @@ -425,9 +436,10 @@ Capistrano::Configuration.instance.load do end desc <<-DESC - Enable ssl for the web server. The SSL cert file should be in - /etc/ssl/certs/default.pem and the SSL key file should be in - /etc/ssl/private/default.key (use the deploy_files task). + Enable ssl for the web server. You'll need to deploy a valid + SSL certificate file to /etc/ssl/certs/default.pem + and a valid SSL key file to /etc/ssl/private/default.key + (use the deploy_files task). DESC task :enable_ssl, :roles => :web_admin do sudo "a2enmod ssl" gem/lib/ec2onrails/recipes.rb @@ -24,7 +24,10 @@ module Ec2onrails #:nodoc: BUGFIX = 1 STRING = [MAJOR, MINOR, TINY, BUGFIX].join('.') - AMI_ID_32_BIT = 'ami-xx' - AMI_ID_64_BIT = 'ami-xx' + AMI_ID_32_BIT_US = 'ami-5394733a' + AMI_ID_64_BIT_US = 'ami-5594733c' + + AMI_ID_32_BIT_EU = 'ami-761c3402' + AMI_ID_64_BIT_EU = 'ami-701c3404' end end gem/lib/ec2onrails/version.rb @@ -1,22 +1,12 @@ h1. EC2 on Rails - h2. Deploy a Ruby on Rails app on EC2 in five minutes -EC2 on Rails is an Ubuntu Linux server image for -"Amazon's EC2 hosting service":http://www.amazon.com/b/ref=sc_fe_l_2/102-6342260-7987311?ie=UTF8&node=201590011&no=3435361 -that's ready to run a standard Ruby on Rails application with little or no customization. -It's a Ruby on Rails "virtual appliance":http://en.wikipedia.org/wiki/Virtual_appliance. +EC2 on Rails is an Ubuntu Linux server image for "Amazon's EC2 hosting service":http://www.amazon.com/b/ref=sc_fe_l_2/102-6342260-7987311?ie=UTF8&node=201590011&no=3435361 that's ready to run a standard Ruby on Rails application with little or no customization. It's a Ruby on Rails "virtual appliance":http://en.wikipedia.org/wiki/Virtual_appliance. -If you have an EC2 account and can start EC2 instances you're five minutes away from deploying -your Rails app. +If you have an EC2 account and can start EC2 instances you're five minutes away from deploying your Rails app. -EC2 on Rails is "opinionated software":http://gettingreal.37signals.com/ch04_Make_Opinionated_Software.php: -the opinion is that for many rails apps the server setup can be generalized -and shared the same way as the web application framework itself. For many people (Twitter, this isn't for you) -the server image can be treated the same way as other shared libraries. And if the day comes when your needs are -unique enough that EC2 on Rails can't be configured to work for you then you can bundle your own image from it -or fork the build source and customize it. +EC2 on Rails is "opinionated software":http://gettingreal.37signals.com/ch04_Make_Opinionated_Software.php: the opinion is that for many rails apps the server setup can be generalized and shared the same way as the web application framework itself. For many people (Twitter, this isn't for you) the server image can be treated the same way as other shared libraries. And if the day comes when your needs are unique enough that EC2 on Rails can't be configured to work for you then you can bundle your own image from it or fork the build source and customize it. But until then, why spend your time configuring servers? @@ -25,8 +15,7 @@ Features of the EC2 image: * Ready to deploy a Rails app with little or no configuration of the server required * Automatic backup of MySQL database to S3 (full backup nightly + incremental backup using binary logs every 5 minutes) * Capistrano tasks to customize the server image, archive and restore the database to/from S3, and more (available as a rubygem) -* Mongrel_cluster behind Apache 2.2, configured according to - "Coda Hale's excellent guide":http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ +* Mongrel_cluster behind Apache 2.2, configured according to "Coda Hale's excellent guide":http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ * Ruby on Rails 2.1.0, 2.0.2 and 1.2.6 * Ruby 1.8.6 * MySQL 5 @@ -38,7 +27,7 @@ Features of the EC2 image: * MySQL, Apache, and syslog configured to use /mnt for data and logging so you don't fill up EC2's small root filesystem * Automatically archives Rails and Apache logs to S3 nightly. * 32-bit and 64-bit images available (supports all instance types, small to extra large). -* Created using a build file, full source is "available":http://rubyforge.org/scm/?group_id=4552 (the EC2 on Rails script is run from "Eric Hammond's EC2 Ubuntu script":http://alestic.com/) +* Created using a build file, full source is "available":http://github.com/pauldowman/ec2onrails/tree/master (the EC2 on Rails script is run from "Eric Hammond's EC2 Ubuntu script":http://alestic.com/) * Can be used as a clustered Rails app running on multiple instances * Automatically runs hourly, daily, weekly and monthly scripts if they exist in Rails application's script directory * Local "Postfix":http://www.postfix.org/ SMTP mail server (only available from within the instance, not listening on external network interfaces) @@ -48,11 +37,15 @@ h2. Using the image This documentation will be improved soon, for now hopefully this covers the basics. -The current AMI id's are: -* ami-c9bc58a0 (32-bit) -* ami-cbbc58a2 (64-bit) +The current AMI id's in the U.S. region are: +* ami-5394733a (32-bit) +* ami-5594733c (64-bit) + +The current AMI id's in the E.U. region are: +* ami-761c3402 (32-bit) +* ami-701c3404 (64-bit) -_I will keep these images for as long as possible, they will not be deleted for at least a few years._ +_I will keep these images available for as long as possible, they will not be deleted for at least a few years._ h4. 1. Install the gem @@ -61,57 +54,34 @@ h4. 1. Install the gem h4. 2. Add the config files to your Rails app -Put "Capfile":http://github.com/pauldowman/ec2onrails/tree/0.9.9.1/documentation/examples/Capfile -in the root of your rails folder, and put -"deploy.rb":http://github.com/pauldowman/ec2onrails/tree/0.9.9.1/documentation/examples/deploy.rb -and -"s3.yml":http://github.com/pauldowman/ec2onrails/tree/0.9.9.1/documentation/examples/s3.yml -in the config folder. +Put "Capfile":http://github.com/pauldowman/ec2onrails/raw/0.9.9.1/documentation/examples/Capfile in the root of your rails folder, and put "deploy.rb":http://github.com/pauldowman/ec2onrails/raw/0.9.9.1/documentation/examples/deploy.rb and "s3.yml":http://github.com/pauldowman/ec2onrails/raw/0.9.9.1/documentation/examples/s3.yml in the config folder. _Be sure to customize those files and read the comments._ -Also, use the hostname "db_primary" in your database.yml file. After running "cap ec2onrails:server:set_roles" it will resolve -to the instance defined in your Capistrano "db" role. +Also, use the hostname "db_primary" in your database.yml file. After running "cap ec2onrails:server:set_roles" it will resolve to the instance defined in your Capistrano "db" role. h4. 4. Start up one or more instances of the image. -There is nothing EC2 on Rails-specific here yet (though soon there will be a Capistrano task to do this for you), -if you've started EC2 instances before you can skip this section. Otherwise, I'm not going to lie, this part is complicated -and will take a lot more than 5 minutes the first time. +There is nothing EC2 on Rails-specific here yet (though soon there will be a Capistrano task to do this for you), if you've started EC2 instances before you can skip this section. Otherwise, I'm not going to lie, this part is complicated and will take a lot more than 5 minutes the first time. -Read the -"running an instance section":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html -in Amazon's getting started guide. +Read the "running an instance section":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html in Amazon's getting started guide. -For the AMI id's of the current images do <code>cap ec2onrails:ami_ids</code> from within the app that you -configured in the previous step (they're also listed earlier on this page). +For the AMI id's of the current images do <code>cap ec2onrails:ami_ids</code> from within the app that you configured in the previous step (they're also listed earlier on this page). _NOTE: Only use the images that match the current version of the gem._ -Please see the "change log":http://github.com/pauldowman/ec2onrails/tree/0.9.9.1/gem/History.txt for release notes, and -see the "list of open issues":http://rubyforge.org/tracker/?atid=17558&group_id=4552&func=browse. +Please see the "change log":http://github.com/pauldowman/ec2onrails/tree/0.9.9.1/gem/History.txt for release notes, and see the "list of open issues":http://rubyforge.org/tracker/?atid=17558&group_id=4552&func=browse. -As is "standard for public AMI's":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/DeveloperGuide/public-ami-guidelines.html, -password-based logins are disabled. You log in with your own -"public/private keypair":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html. +As is "standard for public AMI's":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/DeveloperGuide/public-ami-guidelines.html, password-based logins are disabled. You log in with your own "public/private keypair":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html. -Most basic things can be configured automatically by the Capistrano tasks, but if you want to -you can login by ssh as a user named "admin" (has sudo ability) or as "app" (the user -that the app runs as, does not have sudo ability). The Capistrano tasks automatically -use the app user to deploy the app, and the admin user for server admin tasks -that require sudo. +Most basic things can be configured automatically by the Capistrano tasks, but if you want to you can login by ssh as a user named "admin" (has sudo ability) or as "app" (the user that the app runs as, does not have sudo ability). The Capistrano tasks automatically use the app user to deploy the app, and the admin user for server admin tasks that require sudo. -IMPORTANT: Double-check "your firewall settings":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html. -Be sure that you haven't allowed public access to any ports other than TCP 22 and TCP 80 -(and possibly TCP 443 if you're going to enable HTTPS). -If you're using multiple instances, be sure to allow them network access to each other. +IMPORTANT: Double-check "your firewall settings":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html. Be sure that you haven't allowed public access to any ports other than TCP 22 and TCP 80 (and possibly TCP 443 if you're going to enable HTTPS). If you're using multiple instances, be sure to allow them network access to each other. h4. 5. Copy your public key from the server to keep Capistrano happy -This is a workaround for a quirk in Capistrano. Technically all you should need to connect to the server is the private -key file, the public key is on the server. But for some reason -"Capistrano requires that you have both the public key and the private key files together on the client":http://groups.google.com/group/capistrano/browse_thread/thread/1102208ff925d18. +This is a workaround for a quirk in Capistrano. Technically all you should need to connect to the server is the private key file, the public key is on the server. But for some reason "Capistrano requires that you have both the public key and the private key files together on the client":http://groups.google.com/group/capistrano/browse_thread/thread/1102208ff925d18. There is a Capistrano task that tries to fix this for you. From within the root of your rails app do: @@ -122,25 +92,21 @@ Note, this will only work if you have an external ssh command in the path, it wo h4. 6. Deploy the app with Capistrano -Now that the gem is installed, your deploy.rb is configured and you can start and stop EC2 instances, -this is the only thing you'll need to do from now on. +Now that the gem is installed, your deploy.rb is configured and you can start and stop EC2 instances, this is the only thing you'll need to do from now on. <pre> cap ec2onrails:setup cap deploy:cold </pre> -Yes, it's that easy! The setup task will set the server's timezone, install any -gems and Ubuntu packages that you specified in the config file, and -create your database. +Yes, it's that easy! The setup task will set the server's timezone, install any gems and Ubuntu packages that you specified in the config file, and create your database. That's it, your app is now running on EC2!! h2. Capistrano tasks -"Capistrano":http://capify.org is the most commonly used Rails deployment tool. It comes with many standard "tasks", -and the EC2 on Rails gem includes Capistrano tasks specifically for configuring the server instance. +"Capistrano":http://capify.org is the most commonly used Rails deployment tool. It comes with many standard "tasks", and the EC2 on Rails gem includes Capistrano tasks specifically for configuring the server instance. Capistrano is run from the command-line using the "cap" command, with a task name given as an argument. @@ -152,60 +118,39 @@ You'll mostly need just the following Capistrano tasks: Shows the AMI id's of the images that match the current version of the gem. * <code>cap ec2onrails:setup</code> -This task configures a newly-launched instance. This is the first thing you should do after -starting a new instance. It can be run more than once without ill effect. After running -"cap ec2onrails:setup" the next thing to do is run "cap deploy:cold" +This task configures a newly-launched instance. This is the first thing you should do after starting a new instance. It can be run more than once without ill effect. After running "cap ec2onrails:setup" the next thing to do is run "cap deploy:cold" * <code>cap ec2onrails:server:set_roles</code> -Customizes each instance for it's role(s) (as defined in your Capistrano deploy.rb file). -Run this after starting or stopping instances. -For now this just makes sure that only the appropriate services (Apache, Mongrel, and/or MySQL) -are running. Eventually this will customize settings for the running services also. Note that -an instance can have more than one role. If there's only one instance it will have all roles. +Customizes each instance for it's role(s) (as defined in your Capistrano deploy.rb file). Run this after starting or stopping instances. For now this just makes sure that only the appropriate services (Apache, Mongrel, and/or MySQL) are running. Eventually this will customize settings for the running services also. Note that an instance can have more than one role. If there's only one instance it will have all roles. -Note that due to the way that Capistrano works all tasks are run -against all hosts that are currently defined in the deploy.rb file. -So if you start a new instance then add it to your deploy.rb you will need to run -"cap ec2onrails:setup" again which will be run on all existing instances. +Note that due to the way that Capistrano works all tasks are run against all hosts that are currently defined in the deploy.rb file. So if you start a new instance then add it to your deploy.rb you will need to run "cap ec2onrails:setup" again which will be run on all existing instances. h3. Database management tasks * <code>cap ec2onrails:db:archive</code> -Archive the MySQL database to the bucket specified in your deploy.rb. This is for archiving a snapshot of your -database into any S3 bucket. For example, you might want to do this before deploying. +Archive the MySQL database to the bucket specified in your deploy.rb. This is for archiving a snapshot of your database into any S3 bucket. For example, you might want to do this before deploying. * <code>cap ec2onrails:db:restore</code> -Restore the MySQL database from the bucket specified in your deploy.rb -For example, I use this to restore the current production data (from my actual production backup -bucket) onto a staging server that has the current production version of my -app. I then deploy the new version which tests migrations exactly as they'll -run on the production server. +Restore the MySQL database from the bucket specified in your deploy.rb. For example, I use this to restore the current production data (from my actual production backup bucket) onto a staging server that has the current production version of my app. I then deploy the new version which tests migrations exactly as they'll run on the production server. To get a full list of the Capistrano tasks at any time type <code>cap -T</code> from with your rails app root. h2. Building the image -Building the image is not required, most people will simply use the prebuilt public -image, but there is also a build script that builds the image. It's meant to be called by -"Eric Hammond's EC2 Ubuntu script":http://alestic.com/. +Building the image is not required, most people will simply use the prebuilt public image, but there is also a build script that builds the image. It's meant to be called by "Eric Hammond's EC2 Ubuntu script":http://alestic.com/. h2. Mailing lists -There are two Google groups, one for -"announcements":http://groups.google.com/group/ec2-on-rails-announce -(usually just new release announcements) and one for -"discussion":http://groups.google.com/group/ec2-on-rails-discuss. +There are two Google groups, one for "announcements":http://groups.google.com/group/ec2-on-rails-announce (usually just new release announcements) and one for "discussion":http://groups.google.com/group/ec2-on-rails-discuss. h2. Comments -Comments are welcome. Send an email to "Paul Dowman":http://pauldowman.com/contact/ -or to the "Google group":http://groups.google.com/group/ec2-on-rails-discuss. -If you find bugs please file them -"here":http://rubyforge.org/tracker/?atid=17558&group_id=4552&func=browse -or send me an "email":http://pauldowman.com/contact/. +Comments are welcome. Send an email to "Paul Dowman":http://pauldowman.com/contact/ or to the "Google group":http://groups.google.com/group/ec2-on-rails-discuss. + +If you find bugs please file them "here":http://rubyforge.org/tracker/?atid=17558&group_id=4552&func=browse or send me an "email":http://pauldowman.com/contact/. h2. Change log @@ -216,17 +161,16 @@ See the "change log":http://github.com/pauldowman/ec2onrails/blob/0.9.9.1/gem/Hi h2. How to submit patches Pleae read the "8 steps for fixing other people's code":http://drnicwilliams.com/2007/06/01/8-steps-for-fixing-other-peoples-code/. + The source code can be checked out anonymously using: <pre> git clone git://github.com/pauldowman/ec2onrails.git </pre> -Patches can be submitted to the "RubyForge Tracker":http://rubyforge.org/tracker/?atid=17560&group_id=4552&func=browse -or "emailed directly to me":http://pauldowman.com/contact/ . +Send me a "pull request on Github":http://github.com/pauldowman/ec2onrails/tree, submit a patch to the "RubyForge Tracker":http://rubyforge.org/tracker/?atid=17560&group_id=4552&func=browse or "email me directly":http://pauldowman.com/contact/. h2. License This code is free to use under the terms of the GPL v2. -If you find EC2 on Rails useful please "recommend Paul Dowman":http://www.workingwithrails.com/person/10131-paul-dowman -at Working With Rails. +If you find EC2 on Rails useful please "recommend Paul Dowman":http://www.workingwithrails.com/person/10131-paul-dowman at Working With Rails. gem/website/index.txt 92096662040bd3b2c95bb0b23b8bb0489f19ae77 Paul Dowman paul@pauldowman.com http://github.com/pauldowman/ec2onrails/commit/901ca36e1e2c9f732e8ea52df2d09960842772f2 901ca36e1e2c9f732e8ea52df2d09960842772f2 2009-01-27T16:43:51-08:00 2009-01-27T16:43:51-08:00 updated AMI id's, updated History.txt with new changes and cleaned up web page a0dd8509684a7baed50c0b192d2b43aeec4c8317 Paul Dowman paul@pauldowman.com