We try to keep our books accurate, but sometimes mistakes creep
in. This page lists the errors submitted by our astute readers.
If you've found a new error, please
submit it.
The latest version of the book is P1.0,
released about 1 month ago.
If you've bought a PDF of the book and would like to upgrade
it to this version (for free), visit your
home page.
| PDF |
Paper |
Description |
Found in |
Fixed in |
| 19 |
|
#31639: ">>>>>>> .r32877"
Spurious leftover from svn merge?--Brian Candler
|
B4.0
|
|
|
21 |
#32303: at the bottom of the page, i think the URLs shown for the trunk and the branch should include "svn" rather than "deployit":
svn copy --message="Create the stable branch"
file:///home/ezra/svn/trunk
file:///home/ezra/svn/branches/stable
#32303: at the bottom of the page, i think the URLs shown for the trunk and the branch should include "svn" rather than "deployit":
svn copy --mess ...more... |
P1.0
|
|
|
22 |
#32307: In the merging stable branches section at the top of page 22 in the paper edition of the book, there is a directory path context switch that could use an explanation.
The command on the page (plus the two subsequent ones on page 22):
$ svn merge --revision 422:426 file:///home/ezra/deployit/trunk .
This command should be run from the branches/stable directory path, not from the trunk.
I'm not sure how many people follow the commands step-by-step, but this part could be made more clear. --Henry #32307: In the merging stable branches section at the top of page 22 in the paper edition of the book, there is a directory path context switch that c ...more... |
P1.0
|
|
| 23 |
|
#32270: "We use svn import with the --force option..." does not match up with any code snippet.
--Wayne Conrad
|
B4.0
|
|
| 24 |
|
#31638: The svn mkdir --message "Initial project layout" command is missing the name of the directory that you want to make.
I assume that you want the user to change to /home/ezra/svn, then issue the commands
svn mkdir trunk
svn mkdir tags
svn mkdir branches
But the newbie user would probably have a difficult time knowing this.
Hope this helps,
--Nate--Nathan Neff #31638: The svn mkdir --message "Initial project layout" command is missing the name of the directory that you want to make.
I assume that you want ...more... |
B4.0
|
|
| 25 |
|
#32271: "Database Structure Dumps During Testing: When you run the tests, Rails will dump the development database's structure to db/schema.rb(3)."
It's not apparent what this paragraph is doing here. schema.rb next comes up on page 36. I looked for a command to set a svn:ignore property for db/schema.rb, the perfect reason for this paragraph, but I don't see one.--Wayne Conrad #32271: "Database Structure Dumps During Testing: When you run the tests, Rails will dump the development database's structure to db/schema.rb(3)."
...more... |
B4.0
|
|
| 25 |
|
#31736: Rails 2.0.2 adds the tmp directory as well as tmp/cache tmp/pids tmp/sessions and tmp/sockets. The svn mkdir command errors when using the command specified. --Eric Sendelbach #31736: Rails 2.0.2 adds the tmp directory as well as tmp/cache tmp/pids tmp/sessions and tmp/sockets. The svn mkdir command errors when using the com ...more... |
B4.0
|
|
| 27 |
|
#31640: "I discuss this solution in the (as yet) unwritten sect.vc.deploy.using-capistrano-for-deployingdatabase.yml"
If this is the final beta before publication, you'd better write it soon or else remove this sentence :-)--Brian Candler #31640: "I discuss this solution in the (as yet) unwritten sect.vc.deploy.using-capistrano-for-deployingdatabase.yml"
If this is the final beta bef ...more... |
B4.0
|
|
| 30 |
|
#31674: $ cap deploy_with_migrations
should read:
$ cap deploy:migrations--sideshow
|
B4.0
|
|
|
35 |
#32306: Page 35, under the N+1 Problem:
The code section lists:
friends = Person.find(:all, :conditions => some_friend_connections)
@friend_addresses = person.friends.collect {|friend| friend.address.street}
I believe on the second line, the 'person.friends.collect' should just be 'friends.collect'. The person variable isn't defined in the example (friends is).
This is also in the second example of how to fix the N+1 query with an include statement. --Henry #32306: Page 35, under the N+1 Problem:
The code section lists:
friends = Person.find(:all, :conditions => some_friend_connections)
@friend_add ...more... |
P1.0
|
|
| 38 |
|
#32272: typo:
"has_many()has_one()," should be "has_many(), has one(),"
style:
"belongs_to(), and has_and_belongs_to_many()" doesn't need the comma before "and."
--Wayne Conrad #32272: typo:
"has_many()has_one()," should be "has_many(), has one(),"
style:
"belongs_to(), and has_and_belongs_to_many()" doesn't need th ...more... |
B4.0
|
|
| 83 |
|
#32012: Shouldn't the authme function be
function authme {
ssh $1 -p 8888 ....
}
Just following on from the suggestion above that you should change the default sshd port?--Aditya Sanghi #32012: Shouldn't the authme function be
function authme {
ssh $1 -p 8888 ....
}
Just following on from the suggestion above that you shoul ...more... |
B4.0
|
|
| 85 |
|
#31702: root# sudo gem install rails --no-rdoc --no-ri
Is sudo actually needed? We are already root...--Hywel Mallett
|
B4.0
|
|
| 119 |
|
#31688: "Do a Push Deploy Instead of Pull"
There is a problem with "set :deploy_via, :copy" which caused me a lot of head scratching. SFTP was locking up whenever it connected to my target server.
The solution is to add:
set :synchronous_connect, true
to the recipe. (This is documented in lib/capistrano/configuration/connections.rb if you look really, really hard; the comment is inside a method so it doesn't appear in the rdoc)
Having this hint in the book would have saved me a lot of trouble.
--Brian Candler #31688: "Do a Push Deploy Instead of Pull"
There is a problem with "set :deploy_via, :copy" which caused me a lot of head scratching. SFTP was lock ...more... |
B4.0
|
|
| 121 |
|
#31993: Have you thought about using 'latest_release' instead of 'release_path' for your link_images task? From Capistrano source code: "some tasks, like symlink, need to always point at the latest release, but they can also (occasionally) be called standalone. In the standalone case, the timestamped release_path will be inaccurate, since the directory won't actually exist. This variable lets tasks like symlink work either in the standalone case, or during deployment."--David James #31993: Have you thought about using 'latest_release' instead of 'release_path' for your link_images task? From Capistrano source code: "some tasks, ...more... |
B4.0
|
|
| 128 |
|
#31922: At the bottom of the page where it talks about starting, restarting and stopping the mongrel clusters, I believe there should be a space between "mongrel_cluster_ctl" and "start" (as well as with "stop" and "restart").
Right now it reads:
mongrel_cluster_ctlstart--Steve Kessler #31922: At the bottom of the page where it talks about starting, restarting and stopping the mongrel clusters, I believe there should be a space betwe ...more... |
B4.0
|
|
| 133 |
|
#31683: The cap recipes for restarting, stopping and starting via monit don't work as given (seem to hook into the wrong tasks). The following ones do:
namespace :deploy do
desc <<-DESC
Start Mongrel processes on the app server.
DESC
task :start, :roles => :app do
sudo "/usr/bin/monit start all -g #{monit_group}"
end
desc <<-DESC
Restart the Mongrel processes on the app server by
starting and stopping the cluster.
DESC
task :restart, :roles => :app do
sudo "/usr/bin/monit restart all -g #{monit_group}"
end
desc <<-DESC
Stop the Mongrel processes on the app server.
DESC
task :stop, :roles => :app do
sudo "/usr/bin/monit stop all -g #{monit_group}"
end
end
--Brian Candler #31683: The cap recipes for restarting, stopping and starting via monit don't work as given (seem to hook into the wrong tasks). The following ones do ...more... |
B4.0
|
|
| 143 |
|
#32003: The use of mongrel introduces an issue with multiple processes writing to the log file. It would be helpful to describe configuration of syslog.--John Bito
|
B4.0
|
|
| 170 |
|
#31824: I'd also include the MIME types application/xml application/xhtml+xml text/javascript text/css for the DEFLATE section.--Seth Ladd
|
B4.0
|
|
| 176 |
|
#31701: Space missing: or/foo in 3rd paragraph.--John Bito
|
B4.0
|
|
| 190 |
|
#31703: "In the next chapter, I’ll dive into some basic performance topics."
The next chapter is Deploying on Windows - Performance is the chapter after that.--Hywel Mallett #31703: "In the next chapter, I’ll dive into some basic performance topics."
The next chapter is Deploying on Windows - Performance is the chapter af ...more... |
B4.0
|
|
