railwatch 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: acb264bad21d7d7fb10648e8e67ed6ab0b3253cc4a36a0a0370e3c993bc8cfca
-  data.tar.gz: 77eb54e355a113da4947ed2f83c6dd094f64729f998ccb035e5d4644e11c6d2a
+  metadata.gz: c0487618698d9dc329892ddabb4762ead8838ce593052b9fcb9fe684163dca15
+  data.tar.gz: f0704d125a03f31aee2a0a3b60f40413335703e6eb20296e6153885d7ae9b6fb
 SHA512:
-  metadata.gz: eec5c43f9a2c71846f12d758f1738b576798ab37582a7be0ba28d829e2bc54ae2a8272275c4741a2956bc2e39992eacf3a0493965a69cf94a08142272cfe90b9
-  data.tar.gz: 0cf77dd4e1740c4c919c00bfd0dc3702aaf54a751c8620ba090ab316367b6279c3d7a4cc5b39ac35bc11ab502354699ba93227178365c015e3cf0f64b4cdb77c
+  metadata.gz: fefe712b31d5b060d1f17856da5e7e05ce1303204ecc8c57b4a8ea59a1f2ea0e9bf427ac66b36201450841802ea7327bf17e9a139e5c448fb0deff851ae5c33d
+  data.tar.gz: 41119e84bb12b026516e3cd48dc7fd36835f32a88574e3ad25e8244dd5396925dccf9205ef41171943997adb57062e579784b76b9b3b6e7b63dedd69c1aede52

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.2.2 (2026-09-18)
+
+- README: describe embedded mode. The gem has had two destinations since
+  0.2.0, and the front page still read as though Railwatch Cloud were the
+  only one.
+
 ## 0.2.1 (2026-09-18)
 
 - No change to the gem itself. This release exists to run the automated

data/README.md

@@ -2,10 +2,14 @@
 
 First-class monitoring for Rails. One gem instruments requests, jobs,
 scheduled tasks, commands, queries, exceptions, cache, mail, broadcasts,
-outgoing HTTP, storage, views, and logs, links them into one trace per
-execution, and ships them to Railwatch Cloud for about half a millisecond
-per request plus tens of microseconds per query, with zero writes to your
-database.
+outgoing HTTP, storage, views, and logs, and links them into one trace
+per execution, for about half a millisecond per request plus tens of
+microseconds per query, with zero writes to your database.
+
+Send that to Railwatch Cloud, or keep all of it inside the app:
+[embedded mode](docs/embedded.md) serves the same dashboard at
+`/railwatch` out of two SQLite files your app owns, with no token, no
+Node, no Redis and no job worker.
 
 ## Install
 
@@ -67,6 +71,28 @@ expect { get "/widgets" }.to have_railwatch_queries(at_most: 6)
 expect { get "/widgets" }.not_to have_railwatch_n_plus_one
 ```
 
+## Embedded mode
+
+`--local` keeps everything inside the application. Telemetry goes to two
+SQLite files it owns -- `railwatch` for issues, comments and saved views,
+`railwatch_telemetry` for what the app reports -- and the dashboard is
+served at `/railwatch` from a bundle shipped inside the gem. Nothing
+leaves the machine, and there is nothing else to run.
+
+Puma forks a single writer process (`plugin :railwatch`, which the
+installer adds) that owns both files. The web workers hand it batches
+over a Unix socket instead of writing SQLite on their own threads, and it
+runs the maintenance clock too, so exception grouping, rollups, retention
+and threshold scans happen without a queue.
+
+That dashboard reads every query, log line and exception the app
+produced, so it is closed by default the way Mission Control Jobs is:
+HTTP Basic is on with no credentials, and every request is 401 until you
+set them with `bin/rails railwatch:authentication:configure`. Apps that
+would rather use their own session hand it a `dashboard_user` resolver
+instead. [Embedded mode](docs/embedded.md) covers all of it, including
+upgrades and what it costs to store.
+
 ## Documentation
 
 - [Getting started](docs/getting-started.md) — five-minute install for a

data/lib/railwatch/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Railwatch
-  VERSION = "0.2.1"
+  VERSION = "0.2.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: railwatch
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - Cole Robertson