Question

在我的本地计算机上，我可以通过表单添加新用户，并让rails向他发送电子邮件。但是在heroku上，一切都有效，直到用户提交表单的部分，我希望看到类似“欢迎”页面的内容。这是他在注册后重定向的页面。

production.rb

public function addBrand(Brand $brand)
{
    // key needs to be something that can uniquely identify the brand
    // e.g. name
    $this->getBrands()->set(*key*, $brand);

    return $this;
}

public function removeBrand($key)
{
    $this->getBrands()->remove($key);

    return $this;
}

investors_controller.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 = ENV['RAILS_SERVE_STATIC_FILES'].present?

  # 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

  # 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

  config.action_mailer.delivery_method = :smtp
  # SMTP settings for gmail
  config.action_mailer.smtp_settings = {
   :address              => "smtp.gmail.com",
   :port                 => 587,
   :user_name            => ENV['myemail@gmail.com'],
   :password             => ENV['mypassword'],
   :authentication       => "plain",
   :enable_starttls_auto => true }
end

创建class InvestorsController < ApplicationController def index #change from Investor.first!!! @investor = Investor.first end def show @investor = Investor.find(params[:id]) end def new @investor = Investor.new end def create @investor = Investor.new(user_params) if @investor.save flash[:info] = "Welcome, you're now on your way to success!" render "/static_pages/welcome" InvestorMailer.welcome_email(@investor).deliver_now else render 'new' end end def update if @investor.update_attributes(user_params) flash[:success] = "Updated" else render 'edit' end end private def user_params params.require(:investor).permit(:name, :email, :country, :phone) end end后，从控制器中，我渲染一个模板。该模板在localhost上显示正常但在heroku上没有显示。

我尝试了Investor，但似乎无法找到解决方法。这是我的heroku日志。

heroku pg:reset

Answer 1

对/ investors / new的POST引发了500错误：

2015-06-11T12:05:10.874873+00:00 heroku[router]: at=info method=POST path="/investors" host=infinite-oasis-2303.herokuapp.com request_id=5d322cae-1009-4a4a-b586-acbc1a1bb0be fwd="78.88.252.85" dyno=web.1 connect=2ms service=308ms status=500 bytes=1754

我的猜这与投资者管理员有关...我会检查配置，并确保发送作为我的第一步。

Answer 2

尝试从“/ static_pages / welcome”中删除前导斜杠。 Heroku可能会阻止它作为潜在的安全漏洞。

渲染模板在heroku上不起作用，但在本地起作用

2 个答案: