puma-daemon.gemspec in puma-daemon-0.2.3 vs puma-daemon.gemspec in puma-daemon-0.3.0

- old
+ new

@@ -9,23 +9,21 @@ spec.email = ['kigster@gmail.com'] 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' spec.license = 'MIT' @@ -55,11 +53,9 @@ 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