search

ndbroadbent / turbo-sprockets-rails3

Speeds up your Rails 3 assets:precompile by only recompiling changed files, and only compiling once to generate all assets
MIT License
975 stars 78 forks source link

Required to run rake assets:precompile locally before Capistrano deploy? #57

Open hrp opened 11 years ago

hrp commented 11 years ago

Is it required to run rake assets:precompile locally before a deploy via Capistrano? Is this how the sources_manifest.yml and manifest.yml files get created?

ndbroadbent commented 11 years ago

Hi there, assets:precompile should be run on the server. The assets tasks in capistrano will do this during each deploy.

On Thu, Mar 7, 2013 at 10:20 AM, Hiten Parmar notifications@github.comwrote:

Is it required to run rake assets:precompile locally before a deploy via Capistrano? Is this how the sources_manifest.yml and manifest.yml files get created?

— Reply to this email directly or view it on GitHubhttps://github.com/ndbroadbent/turbo-sprockets-rails3/issues/57 .

hrp commented 11 years ago

That exactly what I thought. I've been struggling with getting the server's assets dir to match my local machine's.

Looking into it, it seemed that the sources_manifest and/or the manifest where different on the server (missing some assets) than on my machine.

Turning off turbo-sprockets seemed to fix the issue. However, I'm unsure if my issue is directly related to turbo-sprockets. At the moment, I can't dive in and figure out all the details. But I want to at some point.

sprestel commented 11 years ago

i have the same problem with some missing assets. Exactly with assets from a gem.

botandrose commented 11 years ago

@hrp did you ever figure anything out here? I'm having the same issue, but only on one of my projects, so I suspect its not solely an issue with turbo-sprockets, as well.

hrp commented 11 years ago

@botandrose I never got a chance to look at this closer.