Ruby on rails Rails在生产中缺少JBuilder hander/模板

我刚刚开始使用JBuilder，并在开发模式下成功地在本地工作

我刚刚将它推送到我的Nginx/Unicorn服务器，每当我尝试查看使用jbuilderjson的url时，我都会得到一个模板丢失错误，并且在：handlers列表中没有JBuilder

缺少模板

缺少模板客户端事件/所有客户端事件用于客户端，应用程序/所有客户端事件用于带有{：locale=>[：en]，：formats=>[：html，：text，：js，：css，：css，：csv，：png，：jpeg，：gif，：bmp，：tiff，：mpeg，：xml，：rss，：atom，：yaml，：多部分表单，：url\u编码表单，：json，：pdf，：zip]，：handlers=>[：erb，：builder，：slim，：haml]}。在以下位置搜索：“//主页/deployer/apps/bigfor blue/releases/201210220934/app/views”

它完全在本地工作，但由于某种原因，当我尝试在生产中运行它时，它不会同意

任何想法都很好

干杯

更新：

Development.rb

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

    # In the development environment your application's code is reloaded on
    # every request. This slows down response time but is perfect for development
    # since you don't have to restart the web server when you make code changes.
    config.cache_classes = false

    # Log error messages when you accidentally call methods on nil.
    config.whiny_nils = true

    # Show full error reports and disable caching
    config.consider_all_requests_local       = true
    config.action_controller.perform_caching = false

    # Print deprecation notices to the Rails logger
    config.active_support.deprecation = :log

    # Only use best-standards-support built into browsers
    config.action_dispatch.best_standards_support = :builtin

    # Raise exception on mass assignment protection for Active Record models
    config.active_record.mass_assignment_sanitizer = :strict

    # Log the query plan for queries taking more than this (works
    # with SQLite, MySQL, and PostgreSQL)
    config.active_record.auto_explain_threshold_in_seconds = 0.5

    # Do not compress assets
    config.assets.compress = false

    # Expands the lines which load the assets
    config.assets.debug = true


    # MAILER

    # Don't care if the mailer can't send
    config.action_mailer.raise_delivery_errors = true

    config.action_mailer.delivery_method = :smtp

    config.action_mailer.default_url_options = { :host => "localhost:3000" }
    ActionMailer::Base.smtp_settings = {
      :address => "smtp.gmail.com",
      :port => 587,
      :authentication => :plain,
      :user_name => "**** TAKEN OUT ****",
      :password => "**** TAKEN OUT ****",
      :openssl_verify_mode => "none"
    }

  end

Production.rb

  BigforBlue::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

    # Full error reports are disabled and caching is turned on
    config.consider_all_requests_local       = true
    config.action_controller.perform_caching = 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.compress = true

    # Don't fallback to assets pipeline if a precompiled asset is missed
    config.assets.compile = false

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

    # Defaults to nil and saved in location specified by config.assets.prefix
    # config.assets.manifest = YOUR_PATH

    # 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

    # See everything in the log (default is :info)
    # 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"

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

    # Disable delivery errors, bad email addresses will be ignored
    # config.action_mailer.raise_delivery_errors = false

    # Enable threaded mode
    # config.threadsafe!

    # 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

    # Log the query plan for queries taking more than this (works
    # with SQLite, MySQL, and PostgreSQL)
    # config.active_record.auto_explain_threshold_in_seconds = 0.5

    # MAILER
    # config.action_mailer.default_url_options = { :host => "http://*** TAKEN OUT ***" }

  end

更新2

我从安装程序中删除了JBuilder，并用RABL替换了它，我仍然存在缺少模板和缺少处理程序的问题

---

因此，它看起来不像是Jbuilder/RABL错误，更像是Unicorn/Nginx错误。

最后，这个问题似乎是由配置或初始Capistrano“cap deploy:setup”或“cap deploy:cold”期间引起的

最后，我从服务器上删除了该应用程序，并执行了新的“cap deploy:setup”和“cap deploy:cold”，修复了问题，JBuilder按预期工作

不知道是什么导致了问题，因为Capistrano配方在第一次错误部署和第二次工作部署之间没有改变

所以我的建议是，如果你遇到这样的问题，完全重新部署你的应用程序可能是一个选择

---

JB

最后，这个问题看起来可能是在配置过程中或在初始Capistrano“cap部署：设置”或“cap部署：冷”过程中引起的

最后，我从服务器上删除了该应用程序，并执行了新的“cap deploy:setup”和“cap deploy:cold”，修复了问题，JBuilder按预期工作

不知道是什么导致了问题，因为Capistrano配方在第一次错误部署和第二次工作部署之间没有改变

所以我的建议是，如果你遇到这样的问题，完全重新部署你的应用程序可能是一个选择

---

JB

您是否在生产中捆绑了

jbuilder

gem？据我所知？当我在服务器上进行“捆绑安装”时，JBuilder会出现在列表中吗？它也在我的Gemfile的主要部分。你能编辑你的帖子并从config/environments中插入development.rb和production.rb文件吗？您好，我已经添加了这两个文件，我还讨论了如何从控制器渲染模板。最初，模板是基于方法名找到自己的，现在我使用“respond_to do | format |”方法。旧方法和新方法都在本地工作，但都会在生产服务器上出现缺少模板的错误。您是否在生产中捆绑了

jbuilder

gem？据我所知？当我在服务器上进行“捆绑安装”时，JBuilder会出现在列表中吗？它也在我的Gemfile的主要部分。你能编辑你的帖子并从config/environments中插入development.rb和production.rb文件吗？您好，我已经添加了这两个文件，我还讨论了如何从控制器渲染模板。最初，模板是基于方法名找到自己的，现在我使用“respond_to do | format |”方法。旧方法和新方法都在本地工作，但都会在生产服务器上出现缺少模板的错误。