Note that there are some explanatory texts on larger screens.

plurals
  1. POUpgrade from rails 3 to rails 4 with capistrano, now image assets are not showing. Why?
    primarykey
    data
    text
    <p>Upgraded from Rails 3 to 4, and now the image assets aren't showing in production. It appears that the javascript and css files are working ok.</p> <p>I've tried the steps at <a href="https://github.com/capistrano/capistrano/wiki/Upgrading-to-Rails-4" rel="nofollow">https://github.com/capistrano/capistrano/wiki/Upgrading-to-Rails-4</a> but it doesn't help.</p> <p>I've tried deleting the json files and yml files in my shared/assets folder, but it still doesn't show the images once the deploy finishes.</p> <p>If I try to view an image on the site in a new tab, I get the "The page you were looking for doesn't exist." error.</p> <p>I've tried this:</p> <pre><code>Bundler.require(:default, Rails.env) </code></pre> <p>and this:</p> <pre><code>if defined?(Bundler) # If you precompile assets before deploying to production, use this line Bundler.require(*Rails.groups(:assets =&gt; %w(development test))) # If you want your assets lazily compiled in production, use this line # Bundler.require(:default, :assets, Rails.env) end </code></pre> <p>in the config/application.rb file. Neither work.</p> <p>Here's what I have in my config/environments/production.rb file:</p> <pre><code>config.serve_static_assets = false config.assets.js_compressor = :uglifier config.assets.compile = false config.assets.digest = true config.assets.version = '1.0' </code></pre> <p>The Capfile:</p> <pre><code>load 'deploy' load 'deploy/assets' load 'config/deploy' </code></pre> <p>What am I doing wrong? How can I get the images to show up in production?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload