puma-daemon 0.2.3 → 0.3.0

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 (7) hide show
  1. checksums.yaml +4 -4
  2. data/.rubocop.yml +3 -0
  3. data/CHANGELOG.md +14 -0
  4. data/Makefile +5 -0
  5. data/lib/puma/daemon/version.rb +1 -1
  6. data/puma-daemon.gemspec +10 -14
  7. metadata +10 -11
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e7b8150de79698d1088f01144bb81576619499a8fe9aef1100ff1af34ba494e6
4
- data.tar.gz: d5d18c2979ed94fffb92a54dcd84c4376bd4fb38496fb0355a4777f7735fc820
3
+ metadata.gz: e8f7fbda428f07fef7dcbc0cc310d87c0d126479119f5c844780b96125b38476
4
+ data.tar.gz: 2e3383565e597d4374f4f6c48343a1d0feef34ebb52db4b401869b27c0dbafde
5
5
  SHA512:
6
- metadata.gz: a4795d230cc70bfe87b7477f0fbbf07e323daf828d0e592bfe7c39f163920102e9fd058e9033aef7861d04b756541816b632f467dcff52e68c847e639f4e2f52
7
- data.tar.gz: 60ff6ab16ece8f09c415e5be2a967df283159d6415d36ab5047c537b23f402fd3c55066e12c488e1f5f812c92dc478f15a305f8081ceb815e655113bfd84242f
6
+ metadata.gz: f94ce039c1665168da3ee3cf187ddc9dac089df2307181bbece7982b5d6694699111d8a135e469fb5c34fe429739bc8af5257116400fc06f455a1fbca0ca3250
7
+ data.tar.gz: cafd7742b52b01a5b0f30e36ddaa66704d9e2790855959833bf75f051cb7d90537922b5487cfb8276e1e29335d14e6c727bba2482cb25d1b1757991717dff22f
data/.rubocop.yml CHANGED
@@ -23,3 +23,6 @@ Layout/LineLength:
23
23
  Naming/FileName:
24
24
  Exclude:
25
25
  - 'lib/puma-daemon.rb'
26
+
27
+ # Gemspec/DevelopmentDependencies:
28
+ # Enabled: false
data/CHANGELOG.md CHANGED
@@ -1,5 +1,19 @@
1
1
  # Changelog
2
2
 
3
+ ## [v0.2.3](https://github.com/kigster/puma-daemon/tree/v0.2.3) (2023-03-14)
4
+
5
+ [Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.2...v0.2.3)
6
+
7
+ **Merged pull requests:**
8
+
9
+ - Attempting to properly track code coverage after fork\(\) [\#15](https://github.com/kigster/puma-daemon/pull/15) ([kigster](https://github.com/kigster))
10
+ - Adding a proper codecov and updating READFME [\#14](https://github.com/kigster/puma-daemon/pull/14) ([kigster](https://github.com/kigster))
11
+ - \[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))
12
+
13
+ ## [v0.2.2](https://github.com/kigster/puma-daemon/tree/v0.2.2) (2023-03-07)
14
+
15
+ [Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.1...v0.2.2)
16
+
3
17
  ## [v0.2.1](https://github.com/kigster/puma-daemon/tree/v0.2.1) (2023-03-07)
4
18
 
5
19
  [Full Changelog](https://github.com/kigster/puma-daemon/compare/v0.2.0...v0.2.1)
data/Makefile CHANGED
@@ -32,6 +32,11 @@ test-all: ## Test all supported Puma Versions
32
32
  make test
33
33
  make puma-v6
34
34
  make test
35
+
36
+ rubocop: ## Run rubocop
37
+ @bundle check || bundle install
38
+ @bundle exec rubocop --format=progress
39
+
35
40
 
36
41
  docker-build-ruby: ## Builds the Docker image by compiling ruby 3.0.0
37
42
  @docker build -f Dockerfile.build -t puma-daemon:latest .
data/lib/puma/daemon/version.rb CHANGED
@@ -2,6 +2,6 @@
2
2
 
3
3
  module Puma
4
4
  module Daemon
5
- VERSION = '0.2.3'
5
+ VERSION = '0.3.0'
6
6
  end
7
7
  end
data/puma-daemon.gemspec CHANGED
@@ -11,19 +11,17 @@ Gem::Specification.new do |spec|
11
11
  spec.summary = "Restore somewhat Puma's ability to self-daemonize, since Puma 5.0 dropped it"
12
12
  spec.description = <<~DESCRIPTION
13
13
 
14
- In version 5.0 the authors of the popular Ruby web server Puma chose
15
- to remove the daemonization support from Puma, because the code wasn't wall maintained,
16
- and because other and perhaps better options exist (such as systemd, etc), not to
17
- mention many people have switched to Kubernetes and Docker, where you want to start
18
- all servers on the foreground.
14
+ In version 5.0 the authors of the popular Ruby web server Puma chose to remove the
15
+ daemonization support from Puma, because the code wasn't wall maintained,
16
+ and because other and better options exist for production deployments. For example
17
+ systemd, Docker/Kubernetes, Heroku, etc.
19
18
 
20
- And yet, something useful and simple got lost — in our humble opinion. Some folks were
21
- indeed happily using the `--daemonize` feature until in 5.0 they got an error that this flag is
22
- not supported.
19
+ Having said that, it was neat and often useful to daemonize Puma in development.
20
+ This gem adds this support to Puma 5 & 6 (hopefully) without breaking anything in Puma
21
+ itself.
23
22
 
24
- So, if you want to use the latest and greatest Puma 5+, but have it self-daemonize,
25
- this gem is for you. Just use *pumad* binary instead of *puma*, or require 'puma/daemon' inside
26
- your config file.
23
+ So, if you want to use the latest and greatest Puma 5+, but prefer to keep using built-in
24
+ daemonization, this gem if for you.
27
25
  DESCRIPTION
28
26
 
29
27
  spec.homepage = 'https://github.com/kigster/puma-daemon'
@@ -57,9 +55,7 @@ Gem::Specification.new do |spec|
57
55
  spec.add_development_dependency 'simplecov'
58
56
  spec.add_development_dependency 'yard'
59
57
 
60
- # Uncomment to register a new dependency of your gem
61
- # spec.add_dependency "example-gem", "~> 1.0"
62
-
63
58
  # For more information and examples about making a new gem, checkout our
64
59
  # guide at: https://bundler.io/guides/creating_gem.html
60
+ spec.metadata['rubygems_mfa_required'] = 'true'
65
61
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: puma-daemon
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.3
4
+ version: 0.3.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Konstantin Gredeskoul
@@ -150,16 +150,14 @@ dependencies:
150
150
  - - ">="
151
151
  - !ruby/object:Gem::Version
152
152
  version: '0'
153
- description: "\nIn version 5.0 the authors of the popular Ruby web server Puma chose\nto
154
- remove the daemonization support from Puma, because the code wasn't wall maintained,
155
- \nand because other and perhaps better options exist (such as systemd, etc), not
156
- to \nmention many people have switched to Kubernetes and Docker, where you want
157
- to start \nall servers on the foreground.\n\nAnd yet, something useful and simple
158
- got lost — in our humble opinion. Some folks were \nindeed happily using the `--daemonize`
159
- feature until in 5.0 they got an error that this flag is \nnot supported.\n\nSo,
160
- if you want to use the latest and greatest Puma 5+, but have it self-daemonize,
161
- \nthis gem is for you. Just use *pumad* binary instead of *puma*, or require 'puma/daemon'
162
- inside\nyour config file.\n"
153
+ description: "\nIn version 5.0 the authors of the popular Ruby web server Puma chose
154
+ to remove the \ndaemonization support from Puma, because the code wasn't wall maintained,\nand
155
+ because other and better options exist for production deployments. For example\nsystemd,
156
+ Docker/Kubernetes, Heroku, etc. \n\nHaving said that, it was neat and often useful
157
+ to daemonize Puma in development.\nThis gem adds this support to Puma 5 & 6 (hopefully)
158
+ without breaking anything in Puma\nitself.\n\nSo, if you want to use the latest
159
+ and greatest Puma 5+, but prefer to keep using built-in\ndaemonization, this gem
160
+ if for you.\n"
163
161
  email:
164
162
  - kigster@gmail.com
165
163
  executables:
@@ -208,6 +206,7 @@ metadata:
208
206
  homepage_uri: https://github.com/kigster/puma-daemon
209
207
  source_code_uri: https://github.com/kigster/puma-daemon
210
208
  changelog_uri: https://github.com/kigster/puma-daemon/blob/master/CHANGELOG.md
209
+ rubygems_mfa_required: 'true'
211
210
  post_install_message:
212
211
  rdoc_options: []
213
212
  require_paths: