Skip to content


Subversion checkout URL

You can clone with
Download ZIP

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: openminds/openminds_deploy
base: eb721e96ba
head fork: openminds/openminds_deploy
compare: 96d6586c7a
  • 2 commits
  • 1 file changed
  • 0 commit comments
  • 2 contributors
Commits on Sep 06, 2011
@petervandenabeele petervandenabeele Expand the README to add asset precompilation for a default Rails 3.1…
… set-up

This might be improved by making a dedicated recipe for this use case.
Commits on Sep 07, 2011
@franklouwers franklouwers Merge pull request #2 from petervandenabeele/master
README expanded for asset precompilation in Rails 3.1
Showing with 13 additions and 0 deletions.
  1. +13 −0 README.rdoc
13 README.rdoc
@@ -55,6 +55,19 @@ If you want to override some settings from the openminds_deploy recipes, define
set :deploy_to, "/home/#{user}/apps/staging/#{application}"
+If you deploy a Rails 3.1 application with the default settings, you need to precompile
+the assets upon deployment. A recipe for a simple case is to append these lines
+to the Capfile.
+ before "deploy:symlink", "deploy:assets"
+ namespace :deploy do
+ desc "Compile assets"
+ task :assets do
+ run "cd #{release_path}; RAILS_ENV=production bundle exec rake assets:precompile"
+ end
+ end
== Recipes in detail
=== openminds_deploy/defaults
This sets up variables like use_sudo and group_writable, enables SSH forwarding, and adds a task to link config/database.yml.

No commit comments for this range

Something went wrong with that request. Please try again.