【问题标题】:Rails assets path is incorrect on new stage with CDN assets pipeline在 CDN 资产管道的新阶段,Rails 资产路径不正确
【发布时间】:2016-08-15 11:47:35
【问题描述】:

我有一个使用 S3 存储桶存储预编译资产的 rails 应用程序。这非常适合制作阶段。

我创建了一个名为“staging”的新阶段,它与生产阶段相同。我复制了 S3 存储桶并为其命名。

但是,当我使用暂存环境部署我的 rails 应用程序时,应用程序资产路径设置为生产阶段路径。

如何让暂存资产指向声明资产路径?

这是我的 config/environments/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

任何帮助将不胜感激。

【问题讨论】:

  • 暂存服务器似乎正在生产阶段运行应用程序。不知道为什么会这样做......

标签: ruby-on-rails asset-pipeline


【解决方案1】:

这是一个长镜头,但是您托管该网站的提供商可以在“生产”模式下运行该网站吗?例如,如果您使用 Heroku,即使您有一个单独的临时应用程序,一切都是“生产”的。

【讨论】:

  • 我的服务器由 BinaryLane 托管,我不使用 Heroku。不过还是谢谢。
猜你喜欢
  • 1970-01-01
  • 2016-07-30
  • 1970-01-01
  • 1970-01-01
  • 2021-01-08
  • 1970-01-01
  • 1970-01-01
  • 2019-09-18
  • 1970-01-01
相关资源
最近更新 更多