Project

General

Custom queries

Profile

Actions
Copy link

Bug #12977

closed

sprockets-rails 2.2.2 or higher is needed for production assets setup

Added by Dominic Cleal over 9 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Dominic Cleal
Category:
Rails
Target version:
1.11.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/3020, https://github.com/theforeman/foreman/pull/3022
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Since #7230, the production environment implicitly requires sprockets-rails 2.2.2 or higher to function, but Rails 4.1.x depends on ~> 2.0 only. The min version should be set in the Gemfile.

config/environments/production.rb relies on getting and setting the Rails app.assets_manifest setting introduced by sprockets-rails 2.2.2 in https://github.com/rails/sprockets-rails/commit/3f26afbaa3d6a5ebe26403c6f42a70a1de96d1d6

Related issues 2 (0 open — 2 closed)

Related to Foreman - Feature #7230: Upgrade Ruby on Rails to 4.1ClosedDaniel Lobato Garcia08/22/2014Actions
Related to Foreman - Bug #13074: sprockets-rails dependency should not be in assets.rb onlyClosedDaniel Lobato Garcia01/08/2016Actions
#1

Updated by Dominic Cleal over 9 years ago

#2

Updated by The Foreman Bot over 9 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3020 added
#4

Updated by Dominic Cleal over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
#5

Updated by The Foreman Bot over 9 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3022 added
#6

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #13074: sprockets-rails dependency should not be in assets.rb only added
Actions
Copy link

Also available in: Atom PDF