Rails 5.2部署Heroku时ActiveModelSerializers报Missing host错误求助

Let's break down why you're hitting this error and how to fix it—local environments work because Rails auto-sets the host for development, but Heroku's production environment needs explicit configuration, especially when using decorators alongside serializers.

Here are the most reliable fixes to try, ordered by likelihood of solving your issue:

1. Ensure Heroku Environment Variable is Set and Configured Correctly #

First, avoid hardcoding the host if you are—Heroku expects dynamic settings to use environment variables.

• Set the host in Heroku: Run this command in your terminal:

  heroku config:set HOST=your-app-name.herokuapp.com
  

  Replace your-app-name with your actual Heroku app name.

• Update production.rb to use the environment variable:
  Open ./config/environments/production.rb and add or update this line:

  Rails.application.routes.default_url_options[:host] = ENV['HOST'] || 'fallback-app-name.herokuapp.com'
  

  The fallback ensures you have a valid value if the environment variable isn't set for some reason.

2. Explicitly Pass Host in Your User Decorator #

The error traces back to user_decorator.rb, which means your decorator's avatar method is generating a URL without access to the default host config. Decorators don't automatically inherit the serializer's context, so you need to specify the host directly.

For example, if your avatar method uses rails_blob_url (for Active Storage) or url_for, modify it like this:

# ./app/decorators/user_decorator.rb
class UserDecorator < ApplicationDecorator
  def avatar_url
    if object.avatar.attached?
      rails_blob_url(object.avatar, host: Rails.application.routes.default_url_options[:host])
    else
      # Fallback URL if no avatar is attached
      '/default-avatar.png'
    end
  end
end

This ensures the URL generator uses the host you configured in production.

3. Sync Serializer Context with Default Host #

If your serializer is calling the decorator method, make sure the serializer itself has access to the host. Update your ApplicationSerializer to include default URL options:

# ./app/serializers/application_serializer.rb
class ApplicationSerializer < ActiveModel::Serializer
  def default_url_options
    { host: Rails.application.routes.default_url_options[:host] }
  end
end

This ensures any URL generation within serializers (or methods they call) uses the correct host, though decorators might still need the explicit host pass as in step 2.

4. Verify Configuration Load Order #

Double-check that your config/application.rb isn't being overridden by production-specific settings. If you set default_url_options in application.rb, make sure production.rb isn't overwriting it with a blank or incorrect value.

Why This Happens Locally vs. Heroku #

In development, Rails automatically sets default_url_options[:host] to localhost:3000, so you never notice the missing config. Production environments (especially Heroku) don't have this default, so every URL generation needs an explicit host.

内容的提问来源于stack exchange，提问作者PrimeTimeTran