memplify 0.3.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a232f7445fef63517859094db7139df93a6dcb8bd6fb2c8be563eabde71058e2
-  data.tar.gz: 39c6d0bd5d14322e6e53b4d844bf9bffeda2142fba820059227fa5373843d292
+  metadata.gz: f5d319c32ed307483484c7edb9054377da25f5e40b8c7315dfaffc7fc69ca262
+  data.tar.gz: 791347aefceff9eea3c2221e151a99f9b5305bc1bad6b6fdb6e2022df7f8bba9
 SHA512:
-  metadata.gz: d1a5cc01df2c26113e04b36fa6a509b48669c2f888aa9251cc367642603a3c9c371080d8681ac3e6ef2860bdb0b9a4ebbd1d8c1c551f4ddf8462f40ad86f43c0
-  data.tar.gz: b9957029d283f1d6cb47175414be764fb4385d04fff0625214692733c0d9323bc1f5508eae04ff3d594481600b63bb6557fdca7461af22015e07a4a8621f4ecc
+  metadata.gz: 995d716de3c0eacd703039863f6e98485cd9439f93f64ed772f9bed237691f755a4c1329ab7b59a86302fe6aed4afda359fa1d86e2cc3a0e2c2fdb588e75d527
+  data.tar.gz: 1494401aa8537f07c9291aa2427c24b971e7655cca7054a05bd4639fa1b5d0e9e429df6367e41eb68f3b690886f7706096dc1043de7a1c9db70939710d20e2e1

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## [Unreleased]
 
+## [0.3.1] - 2025-03-26
+
+- Bump json, rubocop and webmock version due to security issue (https://github.com/tkowalewski/memplify/security/dependabot/1)
+
 ## [0.3.0] - 2025-03-07
 
 - Oh, man. You should forward block to MemoryProfiler

data/README.md

@@ -1,4 +1,4 @@
-# memplify (Proof of concept)
+# memplify
 
 Memplify is a custom reporter ([memplify.com](https://memplify.com)) for [memory_profiler](https://rubygems.org/gems/memory_profiler) gem.
 
@@ -18,11 +18,12 @@ gem install memplify
 
 ## Usage
 
-### Rails
+### Rails applications
 
-Create initializer for memplify: `config/initializers/memplify.rb`
+Create initializer for memplify:
 
 ```ruby
+# config/initializers/memplify.rb
 require "memplify"
 
 Memplify.configure do |configuration|
@@ -30,19 +31,51 @@ Memplify.configure do |configuration|
 end
 ```
 
-For example add memplify middleware for staging environment: `config/environments/staging.rb`
+For example add memplify middleware for staging environment:
 
 ```ruby
+# config/environments/staging.rb
 Rails.application.configure do
   config.middleware.insert(0, Memplify::Middleware)
 end
 ```
 
+### Rack applications
+
+```ruby
+# config.ru
+require "memplify"
+
+Memplify.configure do |configuration|
+  configuration.access_token = "[ACCESS_TOKEN]"
+end
+
+class Application
+  def call(env)
+    status  = 200
+    headers = { "content-type" => "text/html" }
+    body    = ["Kaboom!"]
+
+    [status, headers, body]
+  end
+end
+
+builder = Rack::Builder.new do
+  use Memplify::Middleware if ENV["RACK_ENV"] == "staging"
+
+  map('/') { run Application.new }
+end
+
+run builder
+```
+
+### Other applications / services
+
 You can use memplify also in background jobs and in any place of your app by using reporter directly.
 Just provide report identifier and wrap code with:
 
 ```ruby
-Memplify.report("custom/profile", profile: Rails.env.staging?) do
+Memplify.report("custom/profile", profile: ENV["ENVIRONMENT"] == "staging") do
   # Your code
 end
 ```

data/lib/memplify/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Memplify
-  VERSION = "0.3.0"
+  VERSION = "0.3.1"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: memplify
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
 platform: ruby
 authors:
 - Tomasz Kowalewski
 bindir: exe
 cert_chain: []
-date: 2025-03-07 00:00:00.000000000 Z
+date: 2025-03-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: base64