Question

Question:

How do you get the asset pipeline to process all your .js files? (I want them served individually, not bundled into application.js)

I’m getting a ton of 404’s for the javascript files that my pages are trying to reference:

GET http://<myStagingServer>.heroku.com/assets/<javascriptFilename1_MD5fingerprint> 404 (Not Found)
GET http://<myStagingServer>.heroku.com/assets/<SubDir>/<javascriptFilename2_MD5fingerprint> 404 (Not Found)

I tried adding this to config/application.rb:

config.assets.precompile << '*.js'

But that didn’t do anything as far as I can tell.

Background:

I’m upgrading from Rails 3.0 to 3.1 and enabling the asset pipeline.

Highlights so far:

• Switching to Heroku’s Cedar stack from Bamboo: heroku create --stack cedar.
• Switching to "thin" as the production server, which fixed various issues: gem 'thin'.
• Moving my assets from public/assets to app/assets, updating references in code to use stylesheet_link_tag and javascript_include_tag. (Plus whatever I did for images — they work.)
• Removing x_sendfile_header config options because Heroku doesn’t support it.

Relevant files:

//  
// application.js  
//  
//= require_self  
//  

Answer 1

OMG: I found the problem:

javascripts and stylesheets with periods in their names require explicit extensions

For example:

# WORKS
javascript_include_tag "application"
stylesheet_link_tag "application"

# BROKEN
javascript_include_tag "jueryui.custom"
stylesheet_link_tag "jueryui.custom"

# WORKS
javascript_include_tag "jueryui.custom.js"
stylesheet_link_tag "jueryui.custom.css"

I guess I can see why this is, but I think that it isn’t very well documented on any of the asset pipeline tutorials. Is it common knowledge that you shouldn’t have periods in your asset filenames?