heroku_builder 0.1.4 → 0.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 56df67665e9a0be68a9a25d0afb6ecaf09000841
4
- data.tar.gz: b4b88f8c79a2f8292f6fbc4e49bc6b83f44e7c66
3
+ metadata.gz: e664bec8e4de6657ab2d62b84e6eb2d848c3b469
4
+ data.tar.gz: a8aa0f35d53a9b14d52b6bdd5493f87733f3ec3a
5
5
  SHA512:
6
- metadata.gz: e887330fe7c8b0562314367d2837f56ff3c2264bf0fd814bf1b4b31d4b917c5166373233a5d68416cf6db893feb7c8bfffe5f2ca639c5a6332dbc1ad72551935
7
- data.tar.gz: ed5036a1c3d60514a4bee40d916f24630096ffc6532d10e1fbb8d85f3d3082c553f48ba2d6f31ffd3c1f48912ff9cbf14b2b62280e93b771e7fffe0d1065e56a
6
+ metadata.gz: 283e5e40dcd3ee6ec43e692ea53bd06c587d491c6068b0dbb4ba1a2fac3158447b66ae9c4a2d84bc4516551b7195cb3a7957a98e0225595150f2475be0970db7
7
+ data.tar.gz: 35ea3e3cf41ed6163fc2f8ed16f6dceb3dbe00d5b6825f924d9438d1047d6cf3f8ea226a7552142b851206e5816ab61c6da041b4ccc0c9b045fe14d99813bbde
data/.gitignore CHANGED
@@ -9,3 +9,4 @@
9
9
  /tmp/
10
10
 
11
11
  *.gem
12
+ .env
data/README.md CHANGED
@@ -3,6 +3,13 @@
3
3
 
4
4
  Heroku Builder allows for straight forward configuration of your multi (or single) stage Heroku application as well as dead simple deployment. It uses a YAML configuration to manage a multi-environment configuration, including: configuration variables, resources, add-ons, and git based deployment.
5
5
 
6
+ ## Why
7
+ I wrote this gem to solve two particular problems I've found with Heroku. The first is constructing a new multi-environment application. Setting up a new app isn't hard in Heroku, but building backstage, staging, and production environments that each contain the same core resources, add-ons, and environment variables always resulted in me forgetting something, and spending time troubleshooting.
8
+
9
+ The second, and more common, is for managing environment variables through various stages. We use feature flags and environment variables heavily. This means a code deployment often requires environment variables to be set for features to work correctly. With Heroku Builder, a developer can set Heroku Config-vars in the project code. As the code moves through the various environments, deploying with `rake builder:{environment-name}:apply` will set the Config-vars required for the code changes in addition to deploying code changes.
10
+
11
+ Treating configuration as code allows for peer review, versioning, and a historic view of an application's history. It more completely captures the essence of what is required to run an application.
12
+
6
13
  ## Installation
7
14
 
8
15
  Add this line to your application's Gemfile:
@@ -35,4 +35,7 @@ Gem::Specification.new do |spec|
35
35
  spec.add_development_dependency 'bundler', '~> 1.10'
36
36
  spec.add_development_dependency 'rake', '~> 10.0'
37
37
  spec.add_development_dependency 'rspec', '~> 3.3'
38
+ spec.add_development_dependency 'vcr', '~> 2.9.3'
39
+ spec.add_development_dependency 'simplecov', '~> 0.10'
40
+ spec.add_development_dependency 'dotenv'
38
41
  end
@@ -1,3 +1,3 @@
1
1
  module HerokuBuilder
2
- VERSION = "0.1.4"
2
+ VERSION = '0.1.5'
3
3
  end
@@ -2,12 +2,6 @@ require 'heroku_builder'
2
2
 
3
3
  namespace :builder do
4
4
  # Utility functions from development. These may be removed...
5
- def pretty_print(hsh)
6
- hsh.keys.sort.each do |key|
7
- puts "#{key}: #{hsh[key].inspect}"
8
- end
9
- end
10
-
11
5
  def config_file
12
6
  'config/heroku.yml'
13
7
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: heroku_builder
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.4
4
+ version: 0.1.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jason Vanderhoof
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2015-10-14 00:00:00.000000000 Z
11
+ date: 2015-10-15 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: platform-api
@@ -94,6 +94,48 @@ dependencies:
94
94
  - - "~>"
95
95
  - !ruby/object:Gem::Version
96
96
  version: '3.3'
97
+ - !ruby/object:Gem::Dependency
98
+ name: vcr
99
+ requirement: !ruby/object:Gem::Requirement
100
+ requirements:
101
+ - - "~>"
102
+ - !ruby/object:Gem::Version
103
+ version: 2.9.3
104
+ type: :development
105
+ prerelease: false
106
+ version_requirements: !ruby/object:Gem::Requirement
107
+ requirements:
108
+ - - "~>"
109
+ - !ruby/object:Gem::Version
110
+ version: 2.9.3
111
+ - !ruby/object:Gem::Dependency
112
+ name: simplecov
113
+ requirement: !ruby/object:Gem::Requirement
114
+ requirements:
115
+ - - "~>"
116
+ - !ruby/object:Gem::Version
117
+ version: '0.10'
118
+ type: :development
119
+ prerelease: false
120
+ version_requirements: !ruby/object:Gem::Requirement
121
+ requirements:
122
+ - - "~>"
123
+ - !ruby/object:Gem::Version
124
+ version: '0.10'
125
+ - !ruby/object:Gem::Dependency
126
+ name: dotenv
127
+ requirement: !ruby/object:Gem::Requirement
128
+ requirements:
129
+ - - ">="
130
+ - !ruby/object:Gem::Version
131
+ version: '0'
132
+ type: :development
133
+ prerelease: false
134
+ version_requirements: !ruby/object:Gem::Requirement
135
+ requirements:
136
+ - - ">="
137
+ - !ruby/object:Gem::Version
138
+ version: '0'
97
139
  description: 'Heroku Builder allows for straight forward configuration of your multi
98
140
  (or single) stage Heroku application as well as dead simple deployment. It uses
99
141
  a YAML configuration to manage a multi-environment configuration, including: configuration
@@ -147,7 +189,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
147
189
  version: '0'
148
190
  requirements: []
149
191
  rubyforge_project:
150
- rubygems_version: 2.4.6
192
+ rubygems_version: 2.4.5.1
151
193
  signing_key:
152
194
  specification_version: 4
153
195
  summary: Generate and manage multi-environment Heroku application and simple deployment.