puma-daemon 0.2.3 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e7b8150de79698d1088f01144bb81576619499a8fe9aef1100ff1af34ba494e6
-  data.tar.gz: d5d18c2979ed94fffb92a54dcd84c4376bd4fb38496fb0355a4777f7735fc820
+  metadata.gz: e8f7fbda428f07fef7dcbc0cc310d87c0d126479119f5c844780b96125b38476
+  data.tar.gz: 2e3383565e597d4374f4f6c48343a1d0feef34ebb52db4b401869b27c0dbafde
 SHA512:
-  metadata.gz: a4795d230cc70bfe87b7477f0fbbf07e323daf828d0e592bfe7c39f163920102e9fd058e9033aef7861d04b756541816b632f467dcff52e68c847e639f4e2f52
-  data.tar.gz: 60ff6ab16ece8f09c415e5be2a967df283159d6415d36ab5047c537b23f402fd3c55066e12c488e1f5f812c92dc478f15a305f8081ceb815e655113bfd84242f
+  metadata.gz: f94ce039c1665168da3ee3cf187ddc9dac089df2307181bbece7982b5d6694699111d8a135e469fb5c34fe429739bc8af5257116400fc06f455a1fbca0ca3250
+  data.tar.gz: cafd7742b52b01a5b0f30e36ddaa66704d9e2790855959833bf75f051cb7d90537922b5487cfb8276e1e29335d14e6c727bba2482cb25d1b1757991717dff22f

data/.rubocop.yml

@@ -23,3 +23,6 @@ Layout/LineLength:
 Naming/FileName:
   Exclude:
     - 'lib/puma-daemon.rb'
+
+# Gemspec/DevelopmentDependencies:
+#   Enabled: false

data/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [v0.2.3](https://github.com/kigster/puma-daemon/tree/v0.2.3) (2023-03-14)
+
+[Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.2...v0.2.3)
+
+**Merged pull requests:**
+
+- Attempting to properly track code coverage after fork\(\) [\#15](https://github.com/kigster/puma-daemon/pull/15) ([kigster](https://github.com/kigster))
+- Adding a proper codecov and updating READFME [\#14](https://github.com/kigster/puma-daemon/pull/14) ([kigster](https://github.com/kigster))
+- \[Snyk\] Security upgrade ruby from 3.0.0 to 3.1 [\#12](https://github.com/kigster/puma-daemon/pull/12) ([snyk-bot](https://github.com/snyk-bot))
+
+## [v0.2.2](https://github.com/kigster/puma-daemon/tree/v0.2.2) (2023-03-07)
+
+[Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.1...v0.2.2)
+
 ## [v0.2.1](https://github.com/kigster/puma-daemon/tree/v0.2.1) (2023-03-07)
 
 [Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.0...v0.2.1)

data/Makefile

@@ -32,6 +32,11 @@ test-all:			## Test all supported Puma Versions
 				make test
 				make puma-v6
 				make test
+
+rubocop:			## Run rubocop
+				@bundle check || bundle install
+				@bundle exec rubocop --format=progress
+
 				
 docker-build-ruby:		## Builds the Docker image by compiling ruby 3.0.0
 				@docker build -f Dockerfile.build    -t puma-daemon:latest .

data/lib/puma/daemon/version.rb

@@ -2,6 +2,6 @@
 
 module Puma
   module Daemon
-    VERSION = '0.2.3'
+    VERSION = '0.3.0'
   end
 end

data/puma-daemon.gemspec

@@ -11,19 +11,17 @@ Gem::Specification.new do |spec|
   spec.summary       = "Restore somewhat Puma's ability to self-daemonize, since Puma 5.0 dropped it"
   spec.description   = <<~DESCRIPTION
 
-    In version 5.0 the authors of the popular Ruby web server Puma chose
-    to remove the daemonization support from Puma, because the code wasn't wall maintained, 
-    and because other and perhaps better options exist (such as systemd, etc), not to 
-    mention many people have switched to Kubernetes and Docker, where you want to start 
-    all servers on the foreground.
+    In version 5.0 the authors of the popular Ruby web server Puma chose to remove the 
+    daemonization support from Puma, because the code wasn't wall maintained,
+    and because other and better options exist for production deployments. For example
+    systemd, Docker/Kubernetes, Heroku, etc. 
 
-    And yet, something useful and simple got lost — in our humble opinion. Some folks were 
-    indeed happily using the `--daemonize` feature until in 5.0 they got an error that this flag is 
-    not supported.
+    Having said that, it was neat and often useful to daemonize Puma in development.
+    This gem adds this support to Puma 5 & 6 (hopefully) without breaking anything in Puma
+    itself.
 
-    So, if you want to use the latest and greatest Puma 5+, but have it self-daemonize, 
-    this gem is for you. Just use *pumad* binary instead of *puma*, or require 'puma/daemon' inside
-    your config file.
+    So, if you want to use the latest and greatest Puma 5+, but prefer to keep using built-in
+    daemonization, this gem if for you.
   DESCRIPTION
 
   spec.homepage      = 'https://github.com/kigster/puma-daemon'
@@ -57,9 +55,7 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'simplecov'
   spec.add_development_dependency 'yard'
 
-  # Uncomment to register a new dependency of your gem
-  # spec.add_dependency "example-gem", "~> 1.0"
-
   # For more information and examples about making a new gem, checkout our
   # guide at: https://bundler.io/guides/creating_gem.html
+  spec.metadata['rubygems_mfa_required'] = 'true'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: puma-daemon
 version: !ruby/object:Gem::Version
-  version: 0.2.3
+  version: 0.3.0
 platform: ruby
 authors:
 - Konstantin Gredeskoul
@@ -150,16 +150,14 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description: "\nIn version 5.0 the authors of the popular Ruby web server Puma chose\nto
-  remove the daemonization support from Puma, because the code wasn't wall maintained,
-  \nand because other and perhaps better options exist (such as systemd, etc), not
-  to \nmention many people have switched to Kubernetes and Docker, where you want
-  to start \nall servers on the foreground.\n\nAnd yet, something useful and simple
-  got lost — in our humble opinion. Some folks were \nindeed happily using the `--daemonize`
-  feature until in 5.0 they got an error that this flag is \nnot supported.\n\nSo,
-  if you want to use the latest and greatest Puma 5+, but have it self-daemonize,
-  \nthis gem is for you. Just use *pumad* binary instead of *puma*, or require 'puma/daemon'
-  inside\nyour config file.\n"
+description: "\nIn version 5.0 the authors of the popular Ruby web server Puma chose
+  to remove the \ndaemonization support from Puma, because the code wasn't wall maintained,\nand
+  because other and better options exist for production deployments. For example\nsystemd,
+  Docker/Kubernetes, Heroku, etc. \n\nHaving said that, it was neat and often useful
+  to daemonize Puma in development.\nThis gem adds this support to Puma 5 & 6 (hopefully)
+  without breaking anything in Puma\nitself.\n\nSo, if you want to use the latest
+  and greatest Puma 5+, but prefer to keep using built-in\ndaemonization, this gem
+  if for you.\n"
 email:
 - kigster@gmail.com
 executables:
@@ -208,6 +206,7 @@ metadata:
   homepage_uri: https://github.com/kigster/puma-daemon
   source_code_uri: https://github.com/kigster/puma-daemon
   changelog_uri: https://github.com/kigster/puma-daemon/blob/master/CHANGELOG.md
+  rubygems_mfa_required: 'true'
 post_install_message:
 rdoc_options: []
 require_paths: