Not ideal way to do it, but was proving complicated to have a config file specify which gems for which environments.

Here, we have the billing gem included for the development and test environments only, hardcoded in the Gemfile.

Then we show the links to billing based on a config file setting. The setting itself could be used to specify different types of billing, but isn't yet.

1 files changed, 5 insertions, 1 deletions

diff --git a/Gemfile b/Gemfile
index bdfd9dd..8ca0eaf 100644
--- a/Gemfile
+++ b/Gemfile
@@ -10,18 +10,22 @@ gem "leap_web_core", :path => 'core'
 gem 'leap_web_users', :path => 'users'
 gem 'leap_web_certs', :path => 'certs'
 gem 'leap_web_help', :path => 'help'
-# gem 'leap_web_billing', :path => 'billing'
+# gem 'leap_web_billing', :path => 'billing' # for now, this gem will be included for development and test environments only
 
 # To use debugger
 gem 'debugger', :platforms => :mri_19
 # ruby 1.8 is not supported anymore
 # gem 'ruby-debug', :platforms => :mri_18
 
+group :development do
+  gem 'leap_web_billing', :path => 'billing'
+end
 
 group :test do
   gem 'fake_braintree', require: false
   gem 'capybara', require: false
   gem 'launchy' # so save_and_open_page works in integration tests
+  gem 'leap_web_billing', :path => 'billing'
 end
 
 # unreleased so far ... but leap_web_certs need it