puma-daemon 0.2.2 → 0.3.0

data/codecov.yml

@@ -0,0 +1,4 @@
+comment: 
+  layout: "reach,diff,flags,tree,betaprofiling"
+  show_critical_paths: true
+

data/example/config.ru

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 # config.ru
-run Proc.new { |_env| ['200', {'Content-Type' => 'text/html'}, ['Hello World']] }
+run(proc { |*| ['200', { 'Content-Type' => 'text/html' }, ['Hello World']] })
 # run this with rackup command

data/example/puma.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 require 'puma/daemon'
 
 # The directory to operate out of.
@@ -34,7 +36,7 @@ bind 'tcp://0.0.0.0:9292'
 # Instead of “bind 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'” you
 # can also use the “ssl_bind” option.
 
- # ssl_bind '127.0.0.1', '9292', { key: path_to_key, cert: path_to_cert }
+# ssl_bind '127.0.0.1', '9292', { key: path_to_key, cert: path_to_cert }
 
 # Code to run before doing a restart. This code should
 # close log files, database connections, etc.
@@ -71,6 +73,6 @@ workers 2
 # Check out https://github.com/puma/puma/blob/master/lib/puma/app/status.rb
 # to see what the app has available.
 
-#activate_control_app 'unix:///var/run/pumactl.sock'
+# activate_control_app 'unix:///var/run/pumactl.sock'
 
 daemonize

data/exe/pumad

@@ -1,5 +1,6 @@
 #!/usr/bin/env ruby
 # frozen_string_literal: true
+
 # vim: ft=ruby
 
 lib_path = File.expand_path("#{File.dirname(__FILE__)}/../lib")

data/lib/puma/daemon/runner_adapter.rb

@@ -5,32 +5,44 @@ require_relative 'version'
 module Puma
   module Daemon
     module RunnerAdapter
-      attr_reader :options
-      attr_accessor :has_demonized
-
-      def output_header(mode)
-        super(mode)
-
-        daemonize! if daemon?
-      end
-
-      def daemon?
-        options[:daemon]
-      end
-
-      def daemonize!
-        return if has_demonized
-
-        log '*  Puma Daemon: Demonizing...'
-        log "*  Gem: puma-daemon v#{::Puma::Daemon::VERSION}"
-        log "*  Gem: puma v#{::Puma::Const::VERSION}"
-
-        Process.daemon(true, true)
-        self.has_demonized = true
-      end
-
-      def log(str)
-        super(str) unless str == 'Use Ctrl-C to stop'
+      class << self
+        def included(base)
+          base.class_eval do
+            attr_reader :options
+            attr_accessor :has_demonized
+          end
+
+          base.class_eval do
+            def output_header(mode)
+              super(mode)
+
+              daemonize! if daemon?
+            end
+
+            def daemon?
+              options[:daemon]
+            end
+
+            def daemonize!
+              return if has_demonized
+
+              log '*  Puma Daemon: Demonizing...'
+              log "*  Gem: puma-daemon v#{::Puma::Daemon::VERSION}"
+              log "*  Gem: puma v#{::Puma::Const::VERSION}"
+
+              Process.daemon(true, true)
+              self.has_demonized = true
+            end
+
+            def log(str)
+              if super.respond_to?(:log)
+                super(str) unless str == 'Use Ctrl-C to stop'
+              else
+                puts(str)
+              end
+            end
+          end
+        end
       end
     end
   end

data/lib/puma/daemon/version.rb

@@ -2,6 +2,6 @@
 
 module Puma
   module Daemon
-    VERSION = '0.2.2'
+    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'
@@ -33,7 +31,7 @@ Gem::Specification.new do |spec|
 
   spec.metadata['homepage_uri'] = spec.homepage
   spec.metadata['source_code_uri'] = 'https://github.com/kigster/puma-daemon'
-  spec.metadata['changelog_uri'] = 'https://github.com/kigster/puma-daemon/master/CHANAGELOG.md'
+  spec.metadata['changelog_uri'] = 'https://github.com/kigster/puma-daemon/blob/master/CHANGELOG.md'
 
   # Specify which files should be added to the gem when it is released.
   # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
@@ -50,15 +48,14 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency 'asciidoctor'
   spec.add_development_dependency 'codecov'
+  spec.add_development_dependency 'httparty'
   spec.add_development_dependency 'relaxed-rubocop'
   spec.add_development_dependency 'rspec-its'
   spec.add_development_dependency 'rubocop'
   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,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: puma-daemon
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.3.0
 platform: ruby
 authors:
 - Konstantin Gredeskoul
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-03-07 00:00:00.000000000 Z
+date: 2023-03-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: puma
@@ -66,6 +66,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: httparty
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: relaxed-rubocop
   requirement: !ruby/object:Gem::Requirement
@@ -136,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:
@@ -167,9 +179,11 @@ files:
 - LICENSE.txt
 - Makefile
 - README.adoc
+- README.pdf
 - Rakefile
 - bin/console
 - bin/setup
+- codecov.yml
 - config/puma_cluster.rb
 - config/puma_single.rb
 - example/cluster.sh
@@ -191,7 +205,8 @@ licenses:
 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/master/CHANAGELOG.md
+  changelog_uri: https://github.com/kigster/puma-daemon/blob/master/CHANGELOG.md
+  rubygems_mfa_required: 'true'
 post_install_message:
 rdoc_options: []
 require_paths:
@@ -207,7 +222,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.26
+rubygems_version: 3.3.22
 signing_key:
 specification_version: 4
 summary: Restore somewhat Puma's ability to self-daemonize, since Puma 5.0 dropped