Home/ Questions/Q 6657427
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T01:45:59+00:00

Currently working on a project where we need to drop in various static html

  • 0

Currently working on a project where we need to drop in various static html pages + static assets for those from time to time that “just work.” We cannot have anyone editing the html directly to place paths in for the assets. We need it to simply work such that the html + asset folders are placed directly into /public and the content is served up as it was generated.

When testing this behavior in production, it’s a no go with errors such as:

ActionController::RoutingError (No route matches [GET] "/some_folder/some-image.png"):

I assume this is a result from what I’m reading from 3.1.x’s asset pipeline.

How do you alter the routes such that these will be served up directly? Or is there a preferred way to keep this precise behavior? (Ultimately this will be deployed on heroku.)

Adding some more details as current remarks have not yet pushed my issue over the edge in terms of a solution:

In my present scenario I’m running it straight on WEBrick rails s -e production to test it out. In development mode this does work properly; the only exception is in production.

I am also running this prior to running the server:
bundle exec rake RAILS_ENV=production RAILS_GROUPS=assets assets:precompile --trace

When I actually attempt to load the page in production, I see the following output:

cache: [GET /] miss
cache: [GET /test_files/index.css] miss
cache: [GET /test_files/index.js] miss
cache: [GET /test_files/logo.png] miss
cache: [GET /test_files/background.png] miss
cache: [GET /test_files/horizontal.png] miss
cache: [GET /favicon.ico] miss
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Upon further scrutiny of the production.rb I am seeing: “config.serve_static_assets = true” that when set to false by default evokes the issue experienced in webrick. So when setting that to true it serves the files up properly.

    From some additional reading it appears that perhaps Heroku needs this set to false as well, which is the environment to which we’re deploying.

    Thanks for the input, but this appears to be the approach to take for now and I’d certainly appreciate any further input if this is NOT the correct answer or if there’s a better approach.

    • 0