Ruby on Rails Friday, September 2, 2011

On Fri, Sep 2, 2011 at 6:50 PM, Jim Morris <wolfmanjm@gmail.com> wrote:
the error you are getting running rake assets:precompile locally is that you probably do npt have the production database setup locally and for some reason it tries to connect to the production database, I fixed this error by simply creating the production database locally.

Well, that seems to make some sense, though I don't see why the assets precompilation would hit the database. This is working flawlessly using rc5, so something must have changed in Rails.

I can't help with the other problem as I am still trying to figure out how to deploy these assets, they really seem more trouble than they are worth ;)

Should be relatively easy if you're starting with 3.1, I just added this:
after('deploy:symlink', 'assets:precompile')
namespace :assets do
  desc 'Precompile assets'
  task :precompile, :roles => :app do
    run "cd #{current_path}; RAILS_ENV=#{stage} rake assets:precompile"
  end
end
to the deploy.rb file, pretty standard Capistrano stuff. Never had any problem with the RCs!

But for existing project, it's another story. One coworker tried to convert a big project and gave up after a while as this project already used many complex scss files with lots of @include statements.

I'm eagerly awaiting 3.1.1! ;-)

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment