dash 4.1.1 → 4.1.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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: bb6c271cec9b9ab118649ffeaf503aa5ba31bd8d0f8057ce0a61adb93e130ef4
4
- data.tar.gz: ce7f60b8e4a764e06ab868663f825134d8f73cac0e11f663793e6a12471ab490
3
+ metadata.gz: 1ca6079b920059c7ba0b4740c7a6a992dbecd3538320aadcada8bea2534fd4ae
4
+ data.tar.gz: '089e317ce48dfb5b21f0848d170f5c7db6e15aa2181be2c560c11be0b2ef4847'
5
5
  SHA512:
6
- metadata.gz: 35204403e1680a42ce0b0726225d68c55119a74b387a9cd45189822499e5aa225c250ad82190944cbd4a5ff7aa976b3dcf02600e44b92a8a4ed165f86123c96b
7
- data.tar.gz: cb520eb7f9028fad75e4537afcdcc1c7aea71aa6cb58c35a33b9c8d185781a4de9ad7a9f3d1f1f8daba8b73390b279bbd292ac1a82d531a303f34086c69c28d3
6
+ metadata.gz: a3da6d3bdb662672fdeb2f8c3e8c58e2f651720b11434ad2782eee6516372f0979f0a427267282e166367710ac274e4f4b10b617a9b6cb540e529c212c1de97b
7
+ data.tar.gz: fd2d74330b16950bffa86eecbdf1f00bae67d6264aa664a4a7465c195248f70fe477e2f19a69503c0147c7070cb87c445db0d4bd76f41778ce3348279e207874
@@ -834,7 +834,7 @@ proxy:
834
834
  # below already embeds its ghcr.io host
835
835
  repository: ghcr.io/zoolutions/dash-proxy # Container repository for the
836
836
  # dash-proxy image (this is the default)
837
- version: v1.1.0.1 # Version tag of the dash-proxy image to use.
837
+ version: v1.1.0.2 # Version tag of the dash-proxy image to use.
838
838
  # Defaults to the minimum version this gem
839
839
  # requires - only pin it to roll forward early,
840
840
  # never below the default
@@ -876,6 +876,16 @@ proxy:
876
876
  # supports one, and `http_fallback` falls back to an HTTP-01 challenge when
877
877
  # DNS-01 fails. Both default to true in the proxy.
878
878
  #
879
+ # For `host`/`hosts` names the proxy infers the zone from the name itself.
880
+ # Names learned from `ssl_domains` are tenant-owned and may sit in a zone you
881
+ # do not run DNS for, so from proxy v1.1.0.2 they collapse into a wildcard
882
+ # only where the hash form of `dns_provider` maps their zone explicitly -
883
+ # mapping a zone is you asserting DNS control over it. Under a mapped zone
884
+ # every single-label name is ordered as that zone's wildcard, while the apex
885
+ # and deeper names ride the same order as concrete identifiers. `default` and
886
+ # `auto` assert nothing about a specific zone, so they never collapse a
887
+ # dynamic name.
888
+ #
879
889
  # `directory` overrides the ACME directory URL - point it at Let's Encrypt's
880
890
  # staging environment while you are working out a DNS setup, so you do not
881
891
  # burn production rate limits on failed attempts.
@@ -1,5 +1,5 @@
1
1
  class Dash::Configuration::Proxy::Run
2
- MINIMUM_VERSION = "v1.1.0.1"
2
+ MINIMUM_VERSION = "v1.1.0.2"
3
3
  DEFAULT_HTTP_PORT = 80
4
4
  DEFAULT_HTTPS_PORT = 443
5
5
  DEFAULT_LOG_MAX_SIZE = "10m"
data/lib/dash/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Dash
2
- VERSION = "4.1.1"
2
+ VERSION = "4.1.2"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: dash
3
3
  version: !ruby/object:Gem::Version
4
- version: 4.1.1
4
+ version: 4.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Mikael Henriksson