From 1b893fed99fc77ffcfea40837b53bb0b45c00ec6 Mon Sep 17 00:00:00 2001
From: Paul Hayes and Vinay Patel
 <pairing+fofr+vinayvinay@digital.cabinet-office.gov.uk>
Date: Mon, 8 Sep 2014 07:52:00 +0000
Subject: [PATCH] Moved sass-rails out of the assets group

Publisher deploys are failing because during
assets precompilation, we're seeing an issue
similar to:

https://github.com/twbs/bootstrap-sass/issues/523

This command fails during deploys:

govuk_setenv publisher bundle exec rake \
RAILS_ENV=production RAILS_GROUPS=assets \
assets:precompile

Rails 4 has removed the :assets group from
the generated Gemfile. As mentioned in the
above discussion, it seems OK for gems to
move in that direction and to suggest
removing :assets group:

https://github.com/rails/rails/commit/49c4af43ec5819d8f5c1a91f9b84296c927ce6e7

We have heavy weights like therubyracer in
that group, which has been reported to be
memory intensive. hence i'm avoiding
removing :assets group entirely.

For the current issue, it is sufficient to move
sass-rails out of the :assets group to get assets
to precompile.
---
 Gemfile | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Gemfile b/Gemfile
index 00523f8d1e..de7b0d7a98 100644
--- a/Gemfile
+++ b/Gemfile
@@ -60,9 +60,11 @@ gem 'sidekiq-statsd', '0.1.2'
 # for sidekiq monitoring
 gem 'sinatra', '>= 1.3.0', :require => nil
 
+# NOTE: moved out of the assets group as a workaround for this issue:
+# https://github.com/twbs/bootstrap-sass/issues/523
+gem 'sass-rails', '3.2.6'
 group :assets do
   gem "therubyracer", "0.11.4"
-  gem 'sass-rails', '3.2.6'
   gem 'uglifier', '1.2.7'
 end