Should have been "checking in your *precompiled* assets"...
On Mon, Sep 21, 2015 at 7:13 PM, Robert Fletcher
wrote:
> Checking in your assets isn't ideal, since it makes a mess of your git
> history. Heroku should be able to precompile your assets on the fly, so I'd
> check out the build logs an
Checking in your assets isn't ideal, since it makes a mess of your git
history. Heroku should be able to precompile your assets on the fly, so I'd
check out the build logs and settings in your production.rb file to make
sure they fit the recommended settings. Heroku has some docs on asset
precompil
awesome!
thanks for sharing the solution, it will help the next person
On Mon, Sep 21, 2015 at 2:40 PM, Juan Cabrera wrote:
> I found the solution here:
>
>
> http://stackoverflow.com/questions/16125581/heroku-messing-up-css-following-hartls-rails-tutorial
>
> thanks,
>
> Run bundle exec rake a
I found the solution here:
http://stackoverflow.com/questions/16125581/heroku-messing-up-css-following-hartls-rails-tutorial
thanks,
Run bundle exec rake assets:precompile to compile the assets incl. the
stylesheets into the public hierarchy that is being used by Heroku.
When done:
git add -A
Are you missing some css or something?
I would look in dev-tools in the browser to see if there are any errors.
Areas to investigate:
1. Are there any files that did not get checked in?
2. Are there any css/js files that did not get properly handled by the
asset pipeline?
3. Are there any errors i