lograge_waittime 0.4.1 → 0.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d4b8beb3252b29e69616398793f4d1304b484f9981b011314826ffac886bb564
-  data.tar.gz: 5f4ca7537dbbfb9a04aba58c20ae0881f50e2f05adfd6e72000109570a21f0ee
+  metadata.gz: 8091b0af74830e6c1e7be81df8c280b9666389796891833c8d36073da5d1a7e0
+  data.tar.gz: 11c1fa15d4a937b1e12ff63100e15889ad358fab351ef16e4e1e4bbe361e4824
 SHA512:
-  metadata.gz: afbaa2b0962a326945386faf44548cce985737847ec2e46cce43f8f16d9b304fb5c88326b3a7749425c8d58f25e0cd3f654e04413a6452f3d1aaa98077bc41a8
-  data.tar.gz: 2e700c7e29270e27d3cec1cd04e527554fa4d7e8aff4ee2432f9a0c4b4489d9174b1731906e7f3314f7baee8aaff27452d1aaf998dd44ed2f33779436fb4f1f7
+  metadata.gz: b2291da1e229851b0f3aebcb71794ae0a4a863589b463da6d781486ffc7fced52bfbb099d9b6b96dc9c08087dfb0630039edd40342e61b0e0ba7fa4403fd275c
+  data.tar.gz: 4ecc7ba4b8dc9a5d711bf557b39510decd626eb8e5ee8bf427a0d847e9b17ea401a024f4eb9e456780683c924e8f074fdc421d54c6f17a6ab5bcbfd5aaaf188e

data/CHANGELOG.md

@@ -5,6 +5,11 @@ This project adheres to [Semantic Versioning](http://semver.org/).
 
 ## Unreleased
 
+## 0.4.2 - 2024-11-10
+
+* Testing: Added Rails 7.0 on Ruby 3.2 to test matrix
+* Testing: Added Rails 7.1 and 8.0 on Ruby 3.3 to test matrix
+
 ## 0.4.1 - 2023-02-09
 
 * Testing: Added Rails 7.0 on Ruby 3.1 to test matrix

data/README.md

@@ -27,14 +27,14 @@ Long wait times will feel like a sluggish site for end users, and even though yo
 
 ## Docker demo setup
 
-To quickly get a feel for the parts of the setup, a `docker-compose` sample configuration is included.
+To quickly get a feel for the parts of the setup, a `docker compose` sample configuration is included.
 The setup is fairly simple: requests first hit an NGINX instance, then they are forwarded to the Rails app.
 By looking at the log-output you can observe the request queueing time for each request as `wait`.
 
 Try it out by running:
 
 ```
-docker-compose up
+docker compose up
 ```
 
 Then you can visit [http://localhost:3030/echo](http://localhost:3030/echo) and you will now see the live `wait=` output in the Rails log, like this:
@@ -50,6 +50,8 @@ This next request was through a warmed up stack:
 method=GET path=/echo format=html controller=EchosController action=index status=200 duration=0.60 view=0.28 wait=14.37
 ```
 
+For comparison, you can visit [http://localhost:3020/echo](http://localhost:3020/echo) to see the behaviour when the NGINX queue start header is missing.
+
 ## Installation
 
 ### NGINX change
@@ -60,8 +62,10 @@ proxy_set_header X-Request-Start "t=${msec}";
 ```
 to the relevant part of your server setup. According to [NGINX docs](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header), it can go in one of `http`, `server`, or `location`.
 
+Example from the demo config is at [nginx.conf](docker/web/nginx.conf#L36-L37).
+
 This adds a new header to all incoming requests, with current time in milliseconds as the value.
-`msec` is supported from NGINX releases 1.2.6 and 1.3.9.
+`msec` is supported from NGINX releases 1.2.6 and 1.3.9 (both from 2012).
 
 ### Rails app changes:
 
@@ -72,7 +76,7 @@ bundle add lograge_waittime
 ```
 
 Then add it to your existing lograge initializer, typically in `config/initializers/lograge.rb`.
-If you are just setting up lograge, please check that projects documentation for up to date information.
+If you are just setting up lograge, please check the [lograge projects documentation](https://www.rubydoc.info/gems/lograge/) for up to date information.
 
 ``` ruby
 Rails.application.configure do
@@ -116,12 +120,15 @@ If you prefer a oneliner for testing a combination, try this:
 (asdf shell ruby 3.0.4; export RAILS_VERSION="~> 6.1.0"; rm Gemfile.lock; bundle install; bundle exec rake ci)
 (asdf shell ruby 3.0.4; export RAILS_VERSION="~> 7.0.0"; rm Gemfile.lock; bundle install; bundle exec rake ci)
 (asdf shell ruby 3.1.2; export RAILS_VERSION="~> 7.0.0"; rm Gemfile.lock; bundle install; bundle exec rake ci)
+(asdf shell ruby 3.3.5; export RAILS_VERSION="~> 8.0.0"; rm Gemfile.lock; bundle install; bundle exec rake ci)
 ```
 
 It assumes you have [`asdf`](https://asdf-vm.com/) installed to manage your ruby versions, which is very convenient.
 
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+To install this gem onto your local machine, run `bundle exec rake install`. 
+
+To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
 
 ## Contributing
 

data/lib/lograge_waittime/version.rb

@@ -1,3 +1,3 @@
 module LogrageWaittime
-  VERSION = "0.4.1"
+  VERSION = "0.4.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: lograge_waittime
 version: !ruby/object:Gem::Version
-  version: 0.4.1
+  version: 0.4.2
 platform: ruby
 authors:
 - Laust Rud Jacobsen
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-02-09 00:00:00.000000000 Z
+date: 2024-11-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: lograge
@@ -66,7 +66,7 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-description: 
+description:
 email:
 - laust@valuestream.io
 executables: []
@@ -87,7 +87,7 @@ homepage: https://github.com/rud/lograge_waittime
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -102,8 +102,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
-signing_key: 
+rubygems_version: 3.5.16
+signing_key:
 specification_version: 4
 summary: Add webserver request queueing time to lograge output.
 test_files: []