<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -106,7 +106,8 @@ h4. 5. 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.
 
 &lt;pre&gt;
-cap deploy:cold
+cap ec2onrails:setup
+cap deploy:migrations
 &lt;/pre&gt;
 
 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.</diff>
      <filename>README.textile</filename>
    </modified>
    <modified>
      <diff>@@ -48,13 +48,12 @@ Capistrano::Configuration.instance.load do
   set :use_sudo, false
   set :user, &quot;app&quot;
 
-  #in case any changes were made to the configs
+  # in case anyone is still using deploy:cold
   before &quot;deploy:cold&quot;, &quot;ec2onrails:setup&quot;
   
   after &quot;deploy:symlink&quot;, &quot;ec2onrails:server:set_roles&quot;, &quot;ec2onrails:server:init_services&quot;
-  after &quot;deploy:cold&quot;, &quot;ec2onrails:db:init_backup&quot;, &quot;ec2onrails:db:optimize&quot;, &quot;ec2onrails:server:restrict_sudo_access&quot;
-  # TODO I don't think we can do gem source -a every time because I think it adds the same repo multiple times
-  after &quot;ec2onrails:server:install_gems&quot;, &quot;ec2onrails:server:add_gem_sources&quot;
+  after &quot;deploy:symlink&quot;, &quot;ec2onrails:server:purge_proxy_cache&quot;
+  after &quot;ec2onrails:db:create&quot;, &quot;ec2onrails:db:init_backup&quot;
 
   on :load do
     before &quot;deploy:symlink&quot;, &quot;ec2onrails:server:run_rails_rake_gems_install&quot;</diff>
      <filename>gem/lib/ec2onrails/recipes.rb</filename>
    </modified>
    <modified>
      <diff>@@ -280,20 +280,6 @@ Capistrano::Configuration.instance(:must_exist).load do
       end
       
       desc &lt;&lt;-DESC
-        Add extra gem sources to rubygems (to able to fetch gems from for example gems.github.com).
-        Set ec2onrails_config[:rubygems_sources], it should be with an array of strings.
-      DESC
-      task :add_gem_sources do
-        if cfg[:rubygems_sources]
-          allow_sudo do
-            cfg[:rubygems_sources].each do |gem_source|
-              sudo &quot;gem sources -a #{gem_source}&quot;
-            end
-          end
-        end
-      end
-      
-      desc &lt;&lt;-DESC
         A convenience task to upgrade existing packages and gems and install \
         specified new ones.
       DESC</diff>
      <filename>gem/lib/ec2onrails/recipes/server.rb</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>9a9bab55030a8063de1d2502f2c22e7b966e55af</id>
    </parent>
  </parents>
  <author>
    <name>Paul Dowman</name>
    <email>paul@pauldowman.com</email>
  </author>
  <url>http://github.com/pauldowman/ec2onrails/commit/68d6b9f39a2111ecba7a1bc39ca8c2f1731fe157</url>
  <id>68d6b9f39a2111ecba7a1bc39ca8c2f1731fe157</id>
  <committed-date>2009-10-22T09:19:29-07:00</committed-date>
  <authored-date>2009-10-22T09:19:29-07:00</authored-date>
  <message>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</message>
  <tree>41f8b789559394c8bb0a40d68ea04744af4902ac</tree>
  <committer>
    <name>Paul Dowman</name>
    <email>paul@pauldowman.com</email>
  </committer>
</commit>
