Home/ Questions/Q 8154225
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T16:16:15+00:00

Using Rails 3.2.2 and ruby 1.9.2 and I am not able to serve assets

  • 0

Using Rails 3.2.2 and ruby 1.9.2 and I am not able to serve assets in production. We are running on apache. I’ve read some documentation and set : 

config.serve_static_assets = true
config.assets.compile = true

in production.rb, and it doesn’t seem to work. What else can I try? Or how can I get some debug info on where it IS looking.

Also, I went back to development, and went into assets/images and deleted .png files in order to intentionally break things in the development environment, but it didn’t work, the images still show up. There must be some pre-compiling of assets, but where do they get stored, and how would I clear that? thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Usually, if you have Apache in front of your rails server, you would not want your application to compile assets in production. You probably want to pre-compile assets and have Apache serve them.

    Compiled assets are stored in public/assets by default.

    How all this comes together depends on the particulars of your configuration, which you have not shared. I would recommend reading the rails guides on the asset pipeline:

    http://guides.rubyonrails.org/asset_pipeline.html

    and in particular:

    http://guides.rubyonrails.org/asset_pipeline.html#in-production

    It heven has some examples of how to configure Apache.

    • 0