docker_registry2 1.6.1 → 1.6.2

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.
Files changed (4) hide show
  1. checksums.yaml +5 -5
  2. data/README.md +16 -0
  3. data/lib/registry/version.rb +1 -1
  4. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
- SHA1:
3
- metadata.gz: bf424b2e5e3bfbadd28cafdf008e134209cf2c2e
4
- data.tar.gz: 66e95afc5c4e76d1122d72c1ee6b6d5a828adfce
2
+ SHA256:
3
+ metadata.gz: e35187dcf21e13516ef819f08d95f23f1f398ac8f17b5737dfb829b33d89c431
4
+ data.tar.gz: b5ab54fb96709a4de8c1a32d1c2323bb3b7310b38eaba7978cbfa413b7e64751
5
5
  SHA512:
6
- metadata.gz: 3105398ddc358110e1b38b5c6ce432b65fc4f8dd3c7a1bbfb44bbf5b7d15d597464821c1733dfaa19fdee157e54ee666a9cb3302565f554e73e87d0669796fc9
7
- data.tar.gz: 7c9f6d4a74331433957993a54daa4fb189b813e2a2919c940bbd73aa476336026c2a7879100d55bdb5ea44fc4d3457a17f51889439e353bdb5da04624f79a163
6
+ metadata.gz: d57a17a464cdec565613284bd1168c83ee4e58d23dcb7b3773696f5659c9913d368b1592ad50a4e8778045cde6c36e88185d935ceadabdc86b4c2e34cbc3a6e0
7
+ data.tar.gz: 1fbca82a8c84baac59370e7a68dc97211127e15a3b572a657b82dee16746685d166f80470cb40def9a04a1d8b35c688013b7e6e085bd565b8d7b4ae9a4a51a70
data/README.md CHANGED
@@ -366,6 +366,22 @@ All exceptions thrown inherit from `DockerRegistry2::Exception`.
366
366
  ## Tests
367
367
  The simplest way to test is against a true v2 registry. Thus, the test setup and teardown work against a docker registry. That means that to test, you need a docker engine running. The tests will start up a registry (actually, two registries, to be able to test `copy()`), initialize the data and test against them.
368
368
 
369
+ To run tests, simply run
370
+
371
+ ```sh
372
+ make test
373
+ ```
374
+
375
+ This will run `./test.sh`, which will set up a docker registry in a container, run the tests, and then tear it down.
376
+
377
+ If you are running on a system where you already have a registry against which to run, and/or cannot run `docker` commands, you can pass it the URL to which to connect for tests:
378
+
379
+ ```sh
380
+ make test TEST_REGISTRY=http://registry:5000/ # replace with the URL to your registry
381
+ # or to run manually
382
+ TEST_REGISTRY=http://registry:5000/ ./test.sh
383
+ ```
384
+
369
385
  ## License
370
386
 
371
387
  MIT License.
@@ -1,3 +1,3 @@
1
1
  module DockerRegistry2
2
- VERSION = '1.6.1'
2
+ VERSION = '1.6.2'
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: docker_registry2
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.6.1
4
+ version: 1.6.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Avi Deitcher https://github.com/deitch
@@ -101,7 +101,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
101
101
  version: '0'
102
102
  requirements: []
103
103
  rubyforge_project:
104
- rubygems_version: 2.4.8
104
+ rubygems_version: 2.7.3
105
105
  signing_key:
106
106
  specification_version: 4
107
107
  summary: Docker v2 registry HTTP API client