Errata for Deploying Rails Applications

#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

#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

#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

#33859: The command given to create a stable branch doesn't work. The given command is:

$ svn copy --message "Create the stable branch" ←֓
file:///home/ezra/deployit/trunk ←֓
file:///home/ezra/deployit/branches/stable
Committed revision 234.

The problem is that the path /home/ezra/deployit doesn't exist. The command needed to create the stable branch is:

svn copy --message "Create the stable branch" file:///home/ezra/svn/trunk file:///home/ezra/svn/branches/stable--Chris Bunch

#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

#33429: The authme function will only work if the .ssh directory already exists on the remote server. Also, ssh is very picky about permissions on this directory and the authorized_keys file, so you want to chmod 755 ~/.ssh and chmod 644 ~/.ssh/authorized_keys (if not 600).

#34348: On page 88 there is a guide of how to install nginx. After installing nginx you need to reboot the system (or something similar). Until then the "nginx" command doesn't exist. I think that should be mentioned.--David Trasbo

#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

#33932: The bottom of page 177 reads, "When Capistrano deploys Rails apps, Capistrano appends a time stamp to the URL so that clients will think they are new assets and download them again."

Is that true? I don't think so. I couldn't find anything in the cap docs about it, and my deployed static files don't have custom timestamped filenames. Rails definitely appends cachebreaker timestamps to static files (at least it does to JS and CSS), and I am trying to learn more about exactly when it does that. But I don't think cap has anything to do with it.--Adam