monkrb 0.21.0 → 0.21.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 715184d6d6d9b3d6e50ab43d88d3c8ab7c56db310d0d30d90d67150b9dc28e0d
-  data.tar.gz: 16265638cdde3786734a98c8bd0a743b26e4dca7ea3f253b74c32407ec0ae7f1
+  metadata.gz: fd1a1140ab4c223d2bdd9c10a226ea274e0051af1ab01444194cb4dc88ebb166
+  data.tar.gz: 9fab9365ba1a31224caf14038c2e36c0ba59c9cc70dd60c037f4dbfa78aec8c8
 SHA512:
-  metadata.gz: '097a3550e18dfe987ade8ec24705073b1d0d129fa7303d557acf70ba896186c423d18bb780cbe1e2d6704d7ec8a3706ae163761b7e56225bf7fd651fe0f9163b'
-  data.tar.gz: c1d3e26f194892e893fbdc92a30699fee4b2fbd0424a74bb063b5ca86eda29f76f4909f07e5c44d7211f78d242a1f01f6f36f3d356b37c203d861ffbba97bf83
+  metadata.gz: 36bf94be6268d9f12fbb703132f96b00a84c52e5eeb6b03d9b90b9e981d5c9be2ee89003ecc7952b2880d288454d4d6d1734ffb6cfd8bd70328dded0cbbc1e0e
+  data.tar.gz: 58c8a897231b31edcc82cfd0e3162c64633a2a121f2b3cc01dbbe3b2fa6ef7a7d9760eb2b623a4b6b8def85004322abba20b001758dadd291f8a2ada52b3d26b

data/CHANGELOG.md

@@ -4,6 +4,28 @@ All notable changes to this project are documented here. Format is loosely
 [Keep a Changelog](https://keepachangelog.com/); versions are as released
 in `lib/monk/version.rb`.
 
+## 0.21.1 - 2026-10-09
+
+### Fixed
+
+- **`monk add websocket --transport=postgres` publishes through the
+  `:notify` pool.** `config/websocket.rb` declares
+  `Monk::Persistence::Pg.pool(:notify, size: 1)` and builds
+  `PgFanout.new(..., db_pool: :notify)`, so a process holds one publishing
+  connection however many Ractors publish. Before, every `bin/server`
+  worker opened its own. `AppWebSocket.start!` starts the pool (with
+  Redis it does nothing): `config/load.rb` calls it at the end, which
+  covers `bin/server`, `bin/jobs`, `bin/console` and the tests, and
+  `bin/websocket_server` calls it too. An existing app: replace
+  `config/websocket.rb` with
+  `monk help websocket --file config/websocket.rb --transport=postgres`
+  and add the last lines of `monk help base --file config/load.rb`.
+- **The scaffolded `Dockerfile` builds with `monk add postgres`.** Its
+  builder stage installs `build-essential`: `irb`'s dependencies (`erb`,
+  `io-console`, `prism`) compile native extensions. The image that runs
+  still has no compiler. An existing app: add the `apt-get` line from
+  `monk help base --file Dockerfile`.
+
 ## 0.21.0 - 2026-10-09
 
 ### Changed (breaking)

data/lib/monk/templates/base/Dockerfile

@@ -1,15 +1,19 @@
 # Two-stage build: the builder resolves and installs gems, the final image
 # only keeps the installed bundle plus the app -- no compiler, no gem
-# cache, in the image that actually runs. No system packages needed here:
-# kino ships as precompiled platform gems, and a plain `bundle install`
+# cache, in the image that actually runs. The builder has a compiler for
+# the gems that build a native extension (irb's dependencies, with monk
+# add postgres); kino ships as precompiled platform gems, and pg 1.6+
+# ships precompiled with its own libpq. A plain `bundle install`
 # (Gemfile.lock committed) already resolves every compatible platform, not
 # just the machine that ran it -- nothing to add by hand before building on
 # a different host (docs/guides/deploying.md, "Before the first build").
-# monk/rackup/webrick are pure Ruby, and pg (monk add postgres) 1.6+
-# ships precompiled with its own libpq.
 FROM ruby:4.0-slim AS builder
 WORKDIR /app
 
+RUN apt-get update \
+  && apt-get install -y --no-install-recommends build-essential \
+  && rm -rf /var/lib/apt/lists/*
+
 COPY Gemfile Gemfile.lock* ./
 RUN bundle install
 

data/lib/monk/templates/base/config/load.rb

@@ -24,3 +24,9 @@ end
 %w[models presenters helpers mailers broadcasts jobs].each do |role|
   Dir[File.expand_path("../app/#{role}/**/*.rb", __dir__)].sort.each { |file| require file }
 end
+
+# With websocket (monk add websocket), every process that loads this file
+# can broadcast (bin/server, bin/jobs, bin/console, the tests), so its
+# transport is started here, once everything above has declared its
+# databases.
+AppWebSocket.start! if defined?(AppWebSocket)

data/lib/monk/templates/websocket/agents.md

@@ -18,6 +18,9 @@ over the transport.
   body, never at a file's top level.
 - Only `bin/websocket_server` calls `listen!`; every other process only
   publishes.
+- A process publishes only once `AppWebSocket.start!` has run:
+  `config/load.rb` calls it, so a script that loads `config/websocket.rb`
+  without it calls it itself, at boot, in the main Ractor.
 - With Postgres, a broadcast is capped at just under 8000 bytes (NOTIFY).
 - `WS_ALLOWED_ORIGINS` must list your pages' origins.
 - Switching transports is three steps in SETUP.md, websocket.

data/lib/monk/templates/websocket/bin/websocket_server

@@ -25,6 +25,10 @@ Monk::Bin.run(__FILE__) do
     exit 1
   end
 
+  # A socket's handler can broadcast too (the websocket-chat example does),
+  # so this process publishes like the others.
+  AppWebSocket.start!
+
   # This process holds the sockets, so it's the only one that listens for
   # what the others publish: the transport's subscriber connection opens
   # here, and an unreachable Postgres or Redis fails right here.

data/lib/monk/templates/websocket/config/websocket_postgres.rb

@@ -6,18 +6,32 @@ require_relative "persistence"
 # The WebSocket registry (monk add websocket): which sockets are subscribed
 # to which topics, and how a broadcast reaches them. bin/server, bin/jobs
 # and bin/websocket_server are separate processes, so Postgres
-# LISTEN/NOTIFY carries a broadcast from one to the others, over the
-# :primary connection's settings (config/persistence.rb). A broadcast is
-# capped at just under 8000 bytes, Postgres's NOTIFY limit. To switch to
-# Redis: SETUP.md, websocket.
+# LISTEN/NOTIFY carries a broadcast from one to the others, on the
+# :primary database (config/persistence.rb). A broadcast is capped at just
+# under 8000 bytes, Postgres's NOTIFY limit. To switch to Redis: SETUP.md,
+# websocket.
+#
+# Broadcasts are published through the :notify pool: one connection per
+# process, however many Ractors publish. Size 1, so a page's updates are
+# sent in the order they were made. Declaring it opens nothing:
+# AppWebSocket.start! does, in every process that publishes (config/load.rb
+# and bin/websocket_server call it).
+Monk::Persistence::Pg.pool(:notify, size: 1)
+
 module AppWebSocket
   TRANSPORT = "postgres".freeze
 
   # A registry over this app's transport. bin/websocket_server's (REGISTRY)
-  # also listens; every other process only publishes.
+  # also listens, on a connection of its own; every other process only
+  # publishes.
   def self.build_registry
-    Monk::WebSocket::PgFanout.new(Monk::WebSocket::Registry.new,
-      pg_opts: Monk::Persistence::Pg.connection_options(:primary),)
+    Monk::WebSocket::PgFanout.new(Monk::WebSocket::Registry.new, db_pool: :notify)
+  end
+
+  # Opens the :notify pool's connection. At boot, in the main Ractor, once
+  # every database and pool is declared.
+  def self.start!
+    Monk::Persistence::Pg.start_pools!(:notify)
   end
 
   REGISTRY = build_registry

data/lib/monk/templates/websocket/config/websocket_redis.rb

@@ -17,5 +17,10 @@ module AppWebSocket
     Monk::WebSocket::RedisFanout.new(Monk::WebSocket::Registry.new, redis_url: Monk::Settings[:redis_url])
   end
 
+  # Nothing to open here: each publishing Ractor connects to Redis on its
+  # first broadcast. config/load.rb and bin/websocket_server call it all
+  # the same, as they would with Postgres.
+  def self.start!; end
+
   REGISTRY = build_registry
 end

data/lib/monk/templates/websocket/setup.md

@@ -24,11 +24,14 @@ connect with `wss://`.
 
 1. If the other one isn't installed, add it: `monk add redis` or
    `monk add postgres`.
-2. In `config/websocket.rb`, swap the fanout: `Monk::WebSocket::RedisFanout`
-   with `redis_url: Monk::Settings[:redis_url]` (and `require_relative
-   "redis"`), or `Monk::WebSocket::PgFanout` with
-   `pg_opts: Monk::Persistence::Pg.connection_options(:primary)` (and
-   `require_relative "persistence"`).
+2. Replace `config/websocket.rb` with Monk's version for the other
+   transport (`redis` or `postgres`), then carry over anything you changed
+   in it:
+
+   ```bash
+   monk help websocket --file config/websocket.rb --transport=redis > config/websocket.rb
+   ```
+
 3. Restart `bin/server`, `bin/websocket_server` and `bin/jobs`.
 
 ### Check it works

data/lib/monk/version.rb

@@ -5,5 +5,5 @@ module Monk
   # class of bug .freeze! guards against for routes/error handlers/models,
   # just on a top-level constant that every worker Ractor reads on boot
   # (found live under kino: GET /hello 500'd until this was frozen).
-  VERSION = "0.21.0".freeze
+  VERSION = "0.21.1".freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: monkrb
 version: !ruby/object:Gem::Version
-  version: 0.21.0
+  version: 0.21.1
 platform: ruby
 authors:
 - Matteo Folin