constfig 0.0.1 → 0.0.2

data/.gitignore

@@ -16,3 +16,4 @@ test/tmp
 test/version_tmp
 tmp
 bin/
+tags

data/CHANGELOG

@@ -0,0 +1,7 @@
+# 0.0.2
+
+- improved README
+
+# 0.0.1
+
+- initial version

data/Gemfile

@@ -1,7 +1,9 @@
 source 'https://rubygems.org'
+ruby '1.9.3'
 
 # Specify your gem's dependencies in constfig.gemspec
 gemspec
+gem 'rake'
 gem 'rspec'
 gem 'guard'
 gem 'guard-rspec'

data/README.md

@@ -4,6 +4,9 @@ Simple configuration for Ruby.
 
 Allows you to define configuration CONSTANTS that take values from ENV.
 
+[![Build Status](https://travis-ci.org/astrails/constfig.png)](https://travis-ci.org/astrails/constfig)
+[![Code Climate](https://codeclimate.com/github/astrails/constfig.png)](https://codeclimate.com/github/astrails/constfig)
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -58,7 +61,34 @@ For boolean variables you can supply either `TrueClass`, or  `FalseClass`.
 
 ### Existing constants
 
-This gem will not re-define existing constants.
+This gem will not re-define existing constants, which can be used to define
+defaults for non-production environments.
+
+### Rails on Heroku
+
+There is one caveat with Rails on Heroku. By default Heroku doesn't provide
+environment variables to your application during the `rake assets:precompile`
+stage of slug compilation. If you don't take care of it your application will
+fail to compile its assets and might fail to work in produciton. To take care
+of it you can either use Heroku Labs
+[user-env-compile](https://devcenter.heroku.com/articles/labs-user-env-compile)
+option, or (and this is what I'd recommend) you can use development defaults
+during assets:precompile.
+
+For example in Rails you con do this:
+
+    if Rails.env.development? || Rails.env.test? || ARGV.join =~ /assets:precompile/
+      DEFAULT_DOMAIN = 'myapp.dev'
+    end
+
+    define_config :DEFAULT_DOMAIN
+
+In development and test environments it willuse 'myapp.dev' ad
+`PRIMARY_DOMAIN`, but in production and staging environment it will fail unless
+`PRIMARY_DOMAIN` is provided by environment.
+
+> NOTE: make sure those configuration variables are not actually used for asset
+> compilation. If they are, I'd go with `user-env-compile`.
 
 ### Managing environment
 

data/lib/constfig/version.rb

@@ -1,3 +1,3 @@
 module Constfig
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: constfig
 version: !ruby/object:Gem::Version
-  version: 0.0.1
   prerelease: 
+  version: 0.0.2
 platform: ruby
 authors:
 - Vitaly Kushner
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-05-22 00:00:00.000000000 Z
+date: 2013-05-26 00:00:00.000000000 Z
 dependencies: []
 description: Simple Constnt Configuration for Ruby. Creates CONSTANTS with values
   from ENV
@@ -21,6 +21,7 @@ extra_rdoc_files: []
 files:
 - .gitignore
 - .rspec
+- CHANGELOG
 - Gemfile
 - Guardfile
 - LICENSE.txt
@@ -39,20 +40,26 @@ rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
+      segments:
+      - 0
+      hash: 2038963096202275797
       version: '0'
-required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
+required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
+      segments:
+      - 0
+      hash: 2038963096202275797
       version: '0'
+  none: false
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
 summary: Simple Constnt configuration for Ruby.