orchestration 0.4.6 → 0.4.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b0e5ee806929f885562e72f8d9b646a2c4b349ea9d43efc8d40185de8fc1bd21
-  data.tar.gz: 22d24ea9b0ac4bf3ee4764c74f52bd4721dbb7b96b12de94fd8509998cb6df78
+  metadata.gz: 1de40b0bbbef8c548aa941a18486aa43c7ba6fe8433c9a14acd8cde13fc9e62b
+  data.tar.gz: b7b5cc3303a38971aabdd77217be5cb58ffa9519841724234ed8062854850de7
 SHA512:
-  metadata.gz: f2c0b88548df5da741069990629bfa2d02c6439cdf2c68cc7e9addc8f0d6dbe4074d0ec107f10f7ac235f440c4a422cb6c68eb7d57829c41263cd3ca556edc32
-  data.tar.gz: 63a5b30a5674aef12c730c67cc19e04b64470ae1724516f3bcb9e9fc39bfcc70291c8af1389d1930b4e8dd0fceb844656191d2ee324d50b6ed3aeb0b0f3c1390
+  metadata.gz: fb4c23106ebec66f5eff4d2400a33e7370adffbd201800b4c4a9bda3eea0c5292b97d7011d0e5cf309f23f2ed6a5b4d599010062ee08327dc50d5b99e5a25c1d
+  data.tar.gz: 2fa9e0131222a6b368c321d9dcd314503c96e57ef639551847a17a04c4a624fa5606347ed4fdc80e3fc4535303f4fd93b65d1b241a45879423e137e9865848ad

data/README.md

@@ -35,7 +35,7 @@ The below screenshot demonstrates _Orchestration_ being installed in a brand new
 Add _Orchestration_ to your Gemfile:
 
 ```ruby
-gem 'orchestration', '~> 0.4.6'
+gem 'orchestration', '~> 0.4.7'
 ```
 
 Install:
@@ -150,7 +150,7 @@ make push
 
 ### Development
 
-An [`.env`](https://docs.docker.com/compose/env-file/) is created automatically in your project root. This file is _not_ stored in version control. Set all application environment variables in this file.
+An [`.env` file](https://docs.docker.com/compose/env-file/) is created automatically in your project root. This file is _not_ stored in version control. Set all application environment variables in this file.
 
 #### Launching a development server
 
@@ -184,6 +184,13 @@ Note that _Orchestration_ will wait for all services to become fully available (
 
 _(See [sidecar containers](#sidecar-containers) if you are running your test/development server inside _Docker_)_.
 
+Dependencies will be launched and then tested for readiness. The retry limit and interval time for readiness tests can be controlled by the following environment variables:
+
+```
+ORCHESTRATION_RETRY_LIMIT # default: 10
+ORCHESTRATION_RETRY_INTERVAL # default: 5 [seconds]
+```
+
 ### (Local) Production
 
 Run a production environment locally to simulate your deployment platform:

data/lib/orchestration/service_check.rb

@@ -2,8 +2,8 @@
 
 module Orchestration
   class ServiceCheck
-    ATTEMPT_LIMIT = 10
-    RETRY_INTERVAL = 3 # seconds
+    ATTEMPT_LIMIT = ENV.fetch('ORCHESTRATION_RETRY_LIMIT', '10').to_i
+    RETRY_INTERVAL = ENV.fetch('ORCHESTRATION_RETRY_INTERVAL', '5').to_i
 
     def initialize(service, terminal, options = {})
       @service = service

data/lib/orchestration/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Orchestration
-  VERSION = '0.4.6'
+  VERSION = '0.4.7'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: orchestration
 version: !ruby/object:Gem::Version
-  version: 0.4.6
+  version: 0.4.7
 platform: ruby
 authors:
 - Bob Farrell
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-07-17 00:00:00.000000000 Z
+date: 2019-09-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: database_url