CDNアセットパイプラインの新しいステージで、Rails資産パスが正しくありません

Question

S3バケットを使用してプリコンパイルされたアセットを保存するレールアプリがあります。これは生産段階ではうまくいきます。

プロダクションステージと同じ「ステージング」という新しいステージを作成しました。私はS3のバケットを複製し、別の名前を与えました。

しかし、ステージング環境でレールアプリをデプロイすると、アプリのアセットパスがプロダクションステージのパスに設定されます。

ステージングアセットを指定アセットのパスにするにはどうすればよいですか？

は、ここに私の設定/環境/ staging.rb

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

# Read from yml file 
config.before_configuration do 
    env_file = File.join(Rails.root, 'config', 'local_env.yml') 
    YAML.load(File.open(env_file)).each do |key, value| 
    ENV[key.to_s] = value 
    end if File.exists?(env_file) 
end 

# 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 = 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' 
ENV["AWS_ASSET_DIRECTORY"] = 'website-assets-staging' 
config.action_controller.asset_host = "//#{ENV["AWS_ASSET_DIRECTORY"]}.s3.amazonaws.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.default_url_options = {:host => "staging.website.com.au"} 
config.action_mailer.delivery_method = :smtp 
end 

任意の助けいただければ幸いです。

Answer 1

これは長時間の撮影ですが、サイトを運営しているプロバイダが「運用」モードでサイトを運営している可能性がありますか？たとえば、Herokuを使用している場合、別のステージングアプリを持っていてもすべてが「プロダクション」です。