blocks|key|3019660|text|在config/environment/production.rb中放置一行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3019661|config.assets.compile+=+true|code-block|syntax|javascript|3019662|它的工作原理是在运行时编译资产，就像在开发环境中一样，但它会使应用程序变慢，最好的方法是在生产环境中使用rake+task(RAILS_ENV=production捆绑包执行rake+assets+:预编译)本地编译资产，并将生成的资产提交到公共/资产中，然后进行部署。或者，heroku运行rake资源:预编译|3019663|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

put line in config/environments/production.rb

<pre><code>config.assets.compile = true
</code></pre>

it worked as it will compile the assets on runtime, just like in development environment, but its makes application slow, the best way is to either compile the assets locally in production environment with rake task(RAILS_ENV=production bundle exec rake assets:precompile) and commit your generated assets in public/assets and then do deployment. or, heroku run rake assets:precompile

blocks|key|2807444|text|Heroku发布了一个gem来处理资产，而不需要关闭编译或手动编译。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2807445|https://devcenter.heroku.com/articles/ruby-support#static-assets|offset|length|2807446|只需将其添加到Gemfile并重新部署即可。|2807447|gem+'rails_serve_static_assets',+group:+[:production]|code-block|syntax|javascript|2807448|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1S|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|C]]]]

Heroku released a gem to handle the assets without needing to turn off compilation or to manually compile.

<a href="https://devcenter.heroku.com/articles/ruby-support#static-assets">https://devcenter.heroku.com/articles/ruby-support#static-assets</a>

Just add this to your Gemfile and redeploy.

<pre><code>gem 'rails_serve_static_assets', group: [:production]
</code></pre>

blocks|key|2807480|text|我今天在heroku上用rails+4遇到了这个问题。@Jeff提供的这篇文章有点旧，但是，the+gem+repository有一个很好的自述文件。总而言之，您需要向Gemfile中添加两个gem：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2807481|2807482|gem+'rails_serve_static_assets'+(它将解决静态资产问题)+and|ordered-list-item|style|CODE|2807483|gem+'rails_stdout_logging'+(前一个依赖于它)。|2807484|2807485|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/ruby-support#static-assets^0|1A|I|0|0|0|0|V|0|0|Q|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|Z|8|@$A|10|B|11|H|I]]|9|@]|C|$]]|$1|J|3|K|5|G|7|12|8|@$A|13|B|14|H|I]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

I had this problem today with rails 4 on heroku. The article provided by @Jeff is a little bit old but, <a href="https://devcenter.heroku.com/articles/ruby-support#static-assets">the gem repository</a> has a good readme.
Summarizing, you will need to add two gems to your Gemfile:

<ol>
<li><code>gem 'rails_serve_static_assets'</code> (it will solve the static assets problem) and</li>
<li><code>gem 'rails_stdout_logging'</code> (which the previous one depends on).</li>
</ol>

blocks|key|186439|text|对于Rails+4，使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|186440|config.serve_static_assets+=+true|offset|length|style|CODE|186441|默认值为false。在移除rails_12factor+gem之后，我们需要它。|186442|entityMap^0|0|0|X|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

For Rails 4, use:

<code>config.serve_static_assets = true</code>

The default was false. We needed this after removing the rails_12factor gem.

blocks|key|188451|text|Rails建议默认情况下应禁用此设置config.serve_static_assets，即设置为false。以下是在rails应用程序中生成的config/environments/production.rb中的默认配置|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|188452|禁用Rails的静态资产服务器(Apache或nginx已经这样做了)|188453|config.serve_static_assets+=+false|188454|因此，如果您在本地应用程序中将其设置为true，则仍然可以。但是如果你是在Apache或ngix上部署你的应用，或者在heroku之外的任何系统上部署，那么在你的production.rb配置文件中设置config.serve_static_assets=true是不可取的。以下是Rails指南中的文档。|188455|188456|+config.serve_static_files将Rails本身配置为服务静态文件。默认为true，但在生产环境中是关闭的，因为用于运行应用程序的服务器软件(例如NGINX或Apache)应该服务于静态资产。与默认设置不同，在运行时将其设置为true+(绝对不推荐！)或者使用WEBrick在生产模式下测试应用程序。否则，您将无法使用页面缓存，并且对公共目录下定期存在的文件的请求无论如何都会命中您的Rails应用程序。|blockquote|188457|188458|188459|URL+-+http://guides.rubyonrails.org/configuring.html|188460|entityMap|0|LINK|mutability|MUTABLE|url|http://guides.rubyonrails.org/configuring.html^0|I|Q|20|X|0|0|0|Y|0|2T|V|0|0|0|0|0|6|1A|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1E|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|T|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]]]

Rails recommended that this setting <code>config.serve_static_assets</code> by default should be disabled i.e. set to false. Here is the default configuration in <code>config/environments/production.rb</code> generated in rails app

<h3>Disable Rails's static asset server (Apache or nginx will already do this)</h3>

<code>config.serve_static_assets = false</code>

So if you are setting it to true in your local app then that's still fine. But if you are deploying your app on Apache or ngix or anything other than heroku then its not advisable to make <code>config.serve_static_assets=true</code> in your production.rb config file. Here is the documentation from Rails guides.

<blockquote>
 config.serve_static_files configures Rails itself to serve static
 files. Defaults to true, but in the production environment is turned
 off as the server software (e.g. NGINX or Apache) used to run the
 application should serve static assets instead. Unlike the default
 setting set this to true when running (absolutely not recommended!) or
 testing your app in production mode using WEBrick. Otherwise you won't
 be able use page caching and requests for files that exist regularly
 under the public directory will anyway hit your Rails app.
</blockquote>

URL - <a href="http://guides.rubyonrails.org/configuring.html" rel="nofollow">http://guides.rubyonrails.org/configuring.html</a>

blocks|key|190798|text|要使资产加载每个文件的相应指纹，请验证配置config/environments/production.rb是否具有以下说明：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|190799|ruby+++#+Load+assets+with+fingerprint+behavior+++config.assets.digest+=+true|190800|entityMap^0|L|X|0|0|24|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

To make the assets to load with the corresponding fingerprint of each file verify the configuration <code>config/environments/production.rb</code> has the instruction:

<code>ruby
 # Load assets with fingerprint behavior
 config.assets.digest = true
</code>

I have deployed this app (rails 3.2.11) a million times, I haven't messed with any settings, but now I'm greeted with this:

<img src="https://i.stack.imgur.com/FD7fN.png" alt="enter image description here">

Why did this happen out of the blue? My conents of application.rb include <code>config.assets.enabled = true</code> - never had any issues.

In fact running it locally on port 3000 seems to not have any issues whatsoever.

After deploying to heroku this morning, it seems that it loads nothing that's inside /assets/

Interestingly, after copying the files over to try and just make a new app, <code>git commit</code> results in all the stuff you'd expect as well as a LONG list of these which I think might be related:

<img src="https://i.stack.imgur.com/XjMgB.png" alt="enter image description here">

Edit: Interestingly enough SOME of the assets have loaded, like the logo and the background, but the rest as you can see return 404.

Most of my assets suddenly return 404 after a push to heroku

服务器

我已经部署了这个应用程序(rails 3.2.11)一百万次，我没有弄乱任何设置，但现在我得到了这样的欢迎：​​为什么会突然发生这样的事情？我对application.rb的不满包括config.assets.enabled = true --从来没有遇到过任何问题。实际上，在本地3000端口上运行它似乎没有任何问题。...

问在推送到heroku之后，我的大部分资产突然返回404
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在推送到heroku之后，我的大部分资产突然返回404EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在推送到heroku之后，我的大部分资产突然返回404
EN