ec2onrails 0.9.8 → 0.9.8.1

Sign up to get free protection for your applications and to get access to all the features.
data/History.txt CHANGED
@@ -1,6 +1,14 @@
1
- == 0.9.8 XXXX-XX-XX
1
+ == 0.9.8.1 2007-05-20
2
2
 
3
- * ami-XXXX (32-bit) and ami-XXXX (64-bit)
3
+ * ami-b657b2df (32-bit) and ami-8957b2e0 (64-bit) (same AMI's as 0.9.8, this is an update to the RubyGem only)
4
+ * This is another test release, still not intended to be production-ready. Look for version 1.0. Almost there!!
5
+ * Bug fix: if :ec2onrails[:enable_ssl] = true the setup task fails due to /etc/init.d/apache2 not executable
6
+ * Bug fix: retry the the first mysqld startup, because on first startup sometimes the /etc/init.d/mysql startup script thinks it failed because mysqld took too long to physically write the logs full.
7
+
8
+
9
+ == 0.9.8 2007-05-19
10
+
11
+ * ami-b657b2df (32-bit) and ami-8957b2e0 (64-bit)
4
12
  * This is another test release, still not intended to be production-ready. Look for version 1.0. Almost there!!
5
13
  * Incremental database backups instead of doing a full mysqldump each time (full dump is done once nightly). (Thanks to Markus Bengts for the bug fix)
6
14
  * Added monit monitoring daemon: monitors mysqld, apache, memcached, mongrels, system load and free drive space
@@ -210,7 +210,9 @@ Capistrano::Configuration.instance.load do
210
210
  DESC
211
211
  task :start, :roles => :db_admin do
212
212
  sudo "chmod a+x /etc/init.d/mysql"
213
- sudo "/etc/init.d/mysql start"
213
+ # The mysql init script can fail on the first startup if mysql takes too long
214
+ # to create the logfiles, so try again
215
+ sudo "/etc/init.d/mysql start || (sleep 10 && /etc/init.d/mysql start)"
214
216
  end
215
217
 
216
218
  desc <<-DESC
@@ -444,7 +446,7 @@ Capistrano::Configuration.instance.load do
444
446
  task :enable_ssl, :roles => :web_admin do
445
447
  sudo "a2enmod ssl"
446
448
  sudo "a2ensite default-ssl"
447
- sudo "/etc/init.d/apache2 restart"
449
+ run_init_script("apache2", "restart")
448
450
  end
449
451
  end
450
452
 
@@ -21,7 +21,8 @@ module Ec2onrails #:nodoc:
21
21
  MAJOR = 0
22
22
  MINOR = 9
23
23
  TINY = 8
24
- STRING = [MAJOR, MINOR, TINY].join('.')
24
+ GEM_UPDATE = 1
25
+ STRING = [MAJOR, MINOR, TINY, GEM_UPDATE].join('.')
25
26
 
26
27
  AMI_ID_32_BIT = 'ami-b657b2df'
27
28
  AMI_ID_64_BIT = 'ami-8957b2e0'
data/website/index.html CHANGED
@@ -33,7 +33,7 @@
33
33
  <h1>EC2 on Rails</h1>
34
34
  <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/ec2onrails"; return false'>
35
35
  <p>Get Version</p>
36
- <a href="http://rubyforge.org/projects/ec2onrails" class="numbers">0.9.8</a>
36
+ <a href="http://rubyforge.org/projects/ec2onrails" class="numbers">0.9.8.1</a>
37
37
  </div>
38
38
  <h2>Deploy a Ruby on Rails app on <span class="caps">EC2</span> in five minutes</h2>
39
39
 
@@ -113,8 +113,12 @@ to the instance defined in your Capistrano &#8220;db&#8221; role.</p>
113
113
  <h4>4. Start up one or more instances of the image.</h4>
114
114
 
115
115
 
116
- <p>Soon there will be a Capistrano task to do this for you. In the meantime I&#8217;m not going to lie, this part is complicated
117
- the first time. Read the
116
+ <p>There is nothing <span class="caps">EC2</span> on Rails-specific here yet (though soon there will be a Capistrano task to do this for you),
117
+ if you&#8217;ve started <span class="caps">EC2</span> instances before you can skip this section. Otherwise, I&#8217;m not going to lie, this part is complicated
118
+ the first time.</p>
119
+
120
+
121
+ <p>Read the
118
122
  <a href="http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html">running an instance section</a>
119
123
  in Amazon&#8217;s getting started guide.</p>
120
124
 
@@ -138,7 +142,7 @@ password-based logins are disabled. You log in with your own
138
142
  <p>Most basic things can be configured automatically by the Capistrano tasks, but if you want to
139
143
  you can login by ssh as a user named &#8220;admin&#8221; (has sudo ability) or as &#8220;app&#8221; (the user
140
144
  that the app runs as, does not have sudo ability). The Capistrano tasks automatically
141
- use the app user use to deploy the app, and the admin user for server admin tasks
145
+ use the app user to deploy the app, and the admin user for server admin tasks
142
146
  that require sudo.</p>
143
147
 
144
148
 
@@ -150,12 +154,12 @@ If you&#8217;re using multiple instances, be sure to allow them network access t
150
154
  <h4>5. Copy your public key from the server to keep Capistrano happy</h4>
151
155
 
152
156
 
153
- <p>Technically all you should need to connect to the server is the private key file, the public key is on the server.
154
- But for some reason
157
+ <p>This is a workaround for a quirk in Capistrano. Technically all you should need to connect to the server is the private
158
+ key file, the public key is on the server. But for some reason
155
159
  <a href="http://groups.google.com/group/capistrano/browse_thread/thread/1102208ff925d18">Capistrano requires that you have both the public key and the private key files together on the client</a>.</p>
156
160
 
157
161
 
158
- <p>From within the root of your rails app do:</p>
162
+ <p>There is a Capistrano task that tries to fix this for you. From within the root of your rails app do:</p>
159
163
 
160
164
 
161
165
  <pre>cap ec2onrails:get_public_key_from_server</pre>
@@ -166,6 +170,9 @@ But for some reason
166
170
  <h4>6. Deploy the app with Capistrano</h4>
167
171
 
168
172
 
173
+ <p>Now that the gem is installed, your deploy.rb is configured and you can start and stop <span class="caps">EC2</span> instances, this is the only thing you&#8217;ll need to do from now on.</p>
174
+
175
+
169
176
  <pre>
170
177
  cap ec2onrails:setup
171
178
  cap deploy:cold
data/website/index.txt CHANGED
@@ -65,8 +65,11 @@ to the instance defined in your Capistrano "db" role.
65
65
 
66
66
  h4. 4. Start up one or more instances of the image.
67
67
 
68
- Soon there will be a Capistrano task to do this for you. In the meantime I'm not going to lie, this part is complicated
69
- the first time. Read the
68
+ There is nothing EC2 on Rails-specific here yet (though soon there will be a Capistrano task to do this for you),
69
+ if you've started EC2 instances before you can skip this section. Otherwise, I'm not going to lie, this part is complicated
70
+ the first time.
71
+
72
+ Read the
70
73
  "running an instance section":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html
71
74
  in Amazon's getting started guide.
72
75
 
@@ -85,7 +88,7 @@ password-based logins are disabled. You log in with your own
85
88
  Most basic things can be configured automatically by the Capistrano tasks, but if you want to
86
89
  you can login by ssh as a user named "admin" (has sudo ability) or as "app" (the user
87
90
  that the app runs as, does not have sudo ability). The Capistrano tasks automatically
88
- use the app user use to deploy the app, and the admin user for server admin tasks
91
+ use the app user to deploy the app, and the admin user for server admin tasks
89
92
  that require sudo.
90
93
 
91
94
  Double-check "your firewall settings":http://docs.amazonwebservices.com/AWSEC2/2007-08-29/GettingStartedGuide/running-an-instance.html.
@@ -95,11 +98,11 @@ If you're using multiple instances, be sure to allow them network access to each
95
98
 
96
99
  h4. 5. Copy your public key from the server to keep Capistrano happy
97
100
 
98
- Technically all you should need to connect to the server is the private key file, the public key is on the server.
99
- But for some reason
101
+ This is a workaround for a quirk in Capistrano. Technically all you should need to connect to the server is the private
102
+ key file, the public key is on the server. But for some reason
100
103
  "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.
101
104
 
102
- From within the root of your rails app do:
105
+ There is a Capistrano task that tries to fix this for you. From within the root of your rails app do:
103
106
 
104
107
  <pre>cap ec2onrails:get_public_key_from_server</pre>
105
108
 
@@ -108,6 +111,8 @@ Note, this will only work if you have an external ssh command in the path, it wo
108
111
 
109
112
  h4. 6. Deploy the app with Capistrano
110
113
 
114
+ 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.
115
+
111
116
  <pre>
112
117
  cap ec2onrails:setup
113
118
  cap deploy:cold
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ec2onrails
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.8
4
+ version: 0.9.8.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Paul Dowman
@@ -9,7 +9,7 @@ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
 
12
- date: 2008-05-19 00:00:00 -04:00
12
+ date: 2008-05-20 00:00:00 -04:00
13
13
  default_executable:
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency