Question

使用以rails s -e production开头的生产服务器时，我访问的每个页面都会返回此错误：

We're sorry, but something went wrong.
If you are the application owner check the logs for more information.

我不知道错误意味着什么，或者每次都是同一类型的错误，尽管每次都是相同的文本。

有谁知道为什么会这样？

配置/环境/ production.rb：

Website::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 thread 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 Rails's static asset server (Apache or nginx will already do this).
  config.serve_static_assets = false

  # 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 = false

  # Generate digests for assets URLs.
  config.assets.digest = true

  # Version of your assets, change this if you want to expire all your assets.
  config.assets.version = '1.0'

  # 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

  # Set to :debug to see everything in the log.
  config.log_level = :info

  # 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"

  # Precompile additional assets.
  # application.js, application.css, and all non-JS/CSS in app/assets folder are already added.
  # config.assets.precompile += %w( search.js )

  # 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 can not be found).
  config.i18n.fallbacks = true

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

  # Disable automatic flushing of the log to improve performance.
  # config.autoflush_log = false

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

end

Answer 1

您忘记为Rails应用程序做了一些生产用途准备工作。

确保运行Rails应用程序的用户有权在log目录中写入日志。
确保您的密钥和rails env。用于cookie安全的密钥。 Tou只能创建环境变量，Rails可以反复它export SECRET_KEY_BASE=$(rake secret) Rails用来告诉你在生产模式下运行的Rails应用程序export RAILS_ENV=production
如果配置正确，请确保您的数据库。在运行config/database.yml和rake db:create之后，您需要使用数据库适配器配置创建rake db:migrate。
确保您的资产已预编译。只需运行rake assets:precompile
完成所有这些后，您可以运行rails s

但这不是在生产中运行Rails应用程序的正确方法。为了实现良好和可靠的生产，您需要使用Nginx作为负载平衡器和替代应用程序服务器，例如Puma或Passenger。

每个页面都在我的Rails生产服务器上返回错误

1 个答案: