Alex Rivera | Logout

Rails asset pipeline on staging: correct fingerprint but 404ing

Asked 2011-12-08T02:33:38.517
9

I'm running Rails 3.1.3, which includes Sprockets 2.0.3 as a dependency.

I set up my staging environment to be configured the way the Rails guide suggests for production.

config.serve_static_assets = false
config.assets.compress = true
config.assets.compile = false
config.assets.digest = true

I have included in my Capfile

load 'deploy'
load 'deploy/assets'

And assets get precompiled as expected on deploy.

In public/assets, I find the assets as expected with fingerprints.

application-bd402855d34fb61e0a1690da06f79f20.js
application-bd402855d34fb61e0a1690da06f79f20.js.gz
application-ed3f9a8d23992790841c11b6692fb576.css
application-ed3f9a8d23992790841c11b6692fb576.css.gz
...and a bunch of images...

When I load the page, I see the correct references, fingerprint and all.

<link href="/assets/application-ed3f9a8d23992790841c11b6692fb576.css" media="screen" rel="stylesheet" type="text/css">
<script src="/assets/application-bd402855d34fb61e0a1690da06f79f20.js" type="text/javascript"></script>

However, everything 404s, css, js, images, everything.

Anyone know what the deal is here? Thanks!

Edit
Report

1 Answer

-1
config.assets.compile = false

It should be true

answered 2013-03-13T06:46:59.360

Your Answer