Elastic Beanstalk 不为 Ruby on Rails 加载资产

Question

我有一个 ruby​​ on rails 应用程序，它可以在本地生产中本地运行，但是当我将它上传到 EB 时将无法运行，它破坏了一切。

当它在本地时，它看起来像这样

这是我的 eb 网站，我已将控制台的错误包含在其中，但您明白了

这是我的制作.rb

Rails.application.configure do
  # Settings specified here will take precedence over those in config/application.rb.

  # Code is not reloaded between requests.
  config.cache_classes = true

  # Eager load code on boot. This eager loads most of Rails and
  # your application in memory, allowing both threaded web servers
  # and those relying on copy on write to perform better.
  # Rake tasks automatically ignore this option for performance.
  config.eager_load = true

  # Full error reports are disabled and caching is turned on.
  config.consider_all_requests_local       = false
  config.action_controller.perform_caching = true

  # Enable Rack::Cache to put a simple HTTP cache in front of your application
  # Add `rack-cache` to your Gemfile before enabling this.
  # For large-scale production use, consider using a caching reverse proxy like
  # NGINX, varnish or squid.
  # config.action_dispatch.rack_cache = true

  # Disable serving static files from the `/public` folder by default since
  # Apache or NGINX already handles this.
  config.serve_static_files = true

  # Compress JavaScripts and CSS.
  config.assets.js_compressor = :uglifier
  # config.assets.css_compressor = :sass

  # Do not fallback to assets pipeline if a precompiled asset is missed.
  config.assets.compile = true

  # Asset digests allow you to set far-future HTTP expiration dates on all assets,
  # yet still be able to expire them through the digest params.
  config.assets.digest = true

  # `config.assets.precompile` and `config.assets.version` have moved to config/initializers/assets.rb

  # Specifies the header that your server uses for sending files.
  # config.action_dispatch.x_sendfile_header = 'X-Sendfile' # for Apache
  # config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect' # for NGINX

  # Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
  # config.force_ssl = true

  # Use the lowest log level to ensure availability of diagnostic information
  # when problems arise.
  config.log_level = :debug

  # Prepend all log lines with the following tags.
  # config.log_tags = [ :subdomain, :uuid ]

  # Use a different logger for distributed setups.
  # config.logger = ActiveSupport::TaggedLogging.new(SyslogLogger.new)

  # Use a different cache store in production.
  # config.cache_store = :mem_cache_store

  # Enable serving of images, stylesheets, and JavaScripts from an asset server.
  # config.action_controller.asset_host = 'http://assets.example.com'

  # Ignore bad email addresses and do not raise email delivery errors.
  # Set this to true and configure the email server for immediate delivery to raise delivery errors.
  # config.action_mailer.raise_delivery_errors = false

  # Enable locale fallbacks for I18n (makes lookups for any locale fall back to
  # the I18n.default_locale when a translation cannot be found).
  config.i18n.fallbacks = true

  # Send deprecation notices to registered listeners.
  config.active_support.deprecation = :notify

  # Use default logging formatter so that PID and timestamp are not suppressed.
  config.log_formatter = ::Logger::Formatter.new

  # Do not dump schema after migrations.
  config.active_record.dump_schema_after_migration = false
end

我试过了

  config.serve_static_files = true
  config.assets.compile = true

假的，还是不行。

有什么帮助吗？

Answer 1

这是由于 Nginx 配置（在 /etc/nginx/conf.d/webapp_healthd.conf 中）。
当请求 /assets/anything 时，Nginx 将在 /var/app/current/public/assets 中自行查找。
这意味着 /public/assets 中不存在的任何资产都不会加载

我丑陋的解决方案：

# config/application.rb
config.assets.prefix = '/some_other_path'

请注意，这将减慢资产请求，因为这些请求将由 Puma 处理，而不是由 Nginx 直接处理。

Answer 2

我在将我的 React on Rails 5 应用程序部署到 Elastic Beanstalk 以进行生产时遇到了类似的错误（之前在 Heroku 中的生产环境中）。我从不同的角度来解决，调整nginx默认配置。我的问题是来自public/packs/ 的内容没有被用作packs/，这就是<%= javascript_pack_tag 'application' %> 在app/views/layouts/application.html.erb 中生成链接的方式。我在 /etc/nginx/conf.d/webapp_healthd.conf 的末尾添加了以下位置指令来解决这个问题：

  location /packs {
    alias /var/app/current/public/packs;
    gzip_static on;
    expires 1y;
    add_header Cache-Control public;
    add_header Last-Modified "";
    add_header ETag "";
  }

在 ssh-ing 到应用服务器后，添加此指令和 sudo su; service nginx restart，来自 public/packs/ 的静态内容被正确地提供为 packs/。我相信可以通过.ebextensions 中的配置文件添加此位置指令，以自动更改默认的弹性 beanstalk nginx conf 文件。

Answer 3

如果您使用最新的 Amazon Linux 2 Elastic Beanstalk 平台，那么使用platform configuration 可以更简单地解决此问题。在此处查看完整的详细信息：https://stackoverflow.com/a/69103413/1852005