activeadmin: Sass Precompile failing in Heroku Cedar Stack

I am not sure if this is the place to put this issue, but I am getting the following error in my local assets:precompile command. Here is the full trace:

$ rake assets:precompile --trace ** Invoke assets:precompile (first_time) ** Execute assets:precompile rake aborted! active_admin/nested_menu_arrow.gif isn’t precompiled (in /Users/mattbridges/Sites/frbc-dev/app/assets/stylesheets/active_admin.css.scss)

Tasks: TOP => assets:precompile (See full trace by running task with --trace)

…and I get an entirely different error in Heroku’s Cedar stack

Running: rake assets:precompile rake aborted! could not connect to server: Connection refused Is the server running on host “127.0.0.1” and accepting TCP/IP connections on port 5432?

   Tasks: TOP => environment
   (See full trace by running task with --trace)
   Precompiling assets failed, enabling runtime asset compilation
   Injecting rails31_enable_runtime_asset_compilation

I have no idea what is causing this error. I just ran this on a brand new, no-code-changes app, so no code of my own should be conflicting.

About this issue

Original URL
State: closed
Created 13 years ago
Comments: 37 (10 by maintainers)

Commits related to this issue

Merge pull request #1056 from marcusmateus/helpers_on_precompile Fix for #474: Loads AA SASS helpers in railtie to enable precompile w/o initialization — committed to activeadmin/activeadmin by gregbell 12 years ago

Most upvoted comments

I updated my fix. Instead of putting my dynamic routes in an unless block, I’m breaking out of the entire routes block if it’s precompiling assets. Here’s the snippet I put at the top of the routes block in config/routes.rb:

Myapp::Application.routes.draw |do|
  # The ActiveAdmin routes cause Rails to set up a connection to the
  # production database, which isn't available during
  # assets:precompile on Heroku, so the following unless block skips
  # setting up these routes only when rake assets:precompile is
  # being run.
  #
  # Could be a problem if the assets needed these to be loaded to
  # compile properly; pretty sure they don't.
  break if ARGV.join.include? 'assets:precompile'

benatkin on Nov 12, 2011