orchestration 0.5.9 → 0.5.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5509fae5c79bb804de588e7e15e254c0b460cc35acca4495e9d76006d4f8ba26
-  data.tar.gz: 7dd08a1cd7ccc2a9153062105330f59db5cf669f4c15dfa98cbfb13c438410d5
+  metadata.gz: 150c7f4fbfb486398d0b26e7362b1d913463525d2e3b5d2fd5d3778fa728cc64
+  data.tar.gz: 4c91a0705f955b13aed805b8fa6ce2e4a78177ad81a98177e7ab4a970233a1ff
 SHA512:
-  metadata.gz: 1e89b322c9462c740d6300c1b37d66f4e50b9501f5b570b5d9e369e5b72a031014e728c547891783f181fa15b46846c0a0241ad43a87f5ecdf7cc0acea8b383d
-  data.tar.gz: 3d3846f9d09263614f950a4f1eb1d47b3c52b19ccce2e0522c198b693f352935e26116446307aeea1354c268e32bc7cd82049317961b10053adbc62b587c99b5
+  metadata.gz: 52541a298cbfbbd1f4361370543c428c60fc411e9000a4223dbb865aa02d13931fcf3bce2a3d2b2017b7ffaf12493e6a95b4c333b7352e0476edcd3929d02c93
+  data.tar.gz: 7a617a4b2c7eca3a8b830bb96597934252361be208e1bd545fe4f79067759c709582a59486067c3e7498ac779fa8e6f8c7107725410fabfe80e5d569c42a6ac3

data/README.md

@@ -27,7 +27,7 @@ The below screenshot demonstrates _Orchestration_ being installed in a brand new
 Add _Orchestration_ to your Gemfile:
 
 ```ruby
-gem 'orchestration', '~> 0.5.9'
+gem 'orchestration', '~> 0.5.10'
 ```
 
 Install:
@@ -191,12 +191,20 @@ make serve server='-p 3001 -b 192.168.0.1'
 A default `test` target is provided in your application's main `Makefile`. You are encouraged to modify this target to suit your application's requirements.
 
 To launch all dependency containers, run database migrations, and run tests:
-```
+```bash
 make test
 ```
 
-If you prefer to run tests manually (e.g. if you want to run tests for a specific file) then the `test-setup` target can be used:
+The default `test` command can (and should) be extended. This command is defined in the root `Makefile` in the project and, by defaults, runs `rspec` and `rubocop`.
+
+To run only the `test` command, without test setup (i.e. without restarting containers etc.), pass the `light` option:
+
+```bash
+make test light=1
 ```
+
+If you prefer to run tests manually (e.g. if you want to run tests for a specific file) then the `test-setup` target can be used:
+```bash
 make test-setup
 bundle exec rspec spec/my_class_spec.rb
 ```

data/lib/orchestration/docker_compose/configuration.rb

@@ -62,7 +62,7 @@ module Orchestration
           .fetch(service)
           .new(config, @environment)
           .definition
-          &.merge('networks' => { 'local' => {} })
+          &.tap { |definition| definition['networks'] ||= { 'local' => {} } }
       end
     end
   end

data/lib/orchestration/templates/env.erb

@@ -2,5 +2,3 @@
 # e.g.:
 #
 # DISABLE_SPRING=1
-
-PUBLISH_PORT=3000

data/lib/orchestration/templates/orchestration.mk.erb

@@ -112,7 +112,7 @@ all: build
 
 .PHONY: start
 ifndef network
-start: network := ${compose_project_name}_default
+start: network := ${compose_project_name}
 endif
 start: _create-log-directory _clean-logs
 	@$(call print,'${yellow}Starting ${cyan}${env}${yellow} containers${reset} ...')

data/lib/orchestration/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: orchestration
 version: !ruby/object:Gem::Version
-  version: 0.5.9
+  version: 0.5.10
 platform: ruby
 authors:
 - Bob Farrell
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-01-18 00:00:00.000000000 Z
+date: 2021-01-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: database_url