Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

Relationships

#1532 Add --server support to serve reload

Opened by stack72 · 8/5/2026· Shipped 8/5/2026

Problem

swamp serve reload currently works by reading .swamp/serve.pid and sending SIGHUP to the local process, which means it only works on the same box as the server. Remote users have no way to trigger a reload.

Proposed Solution

Add --server support to serve reload using the same request-response WebSocket pattern as access reload:

  1. Add a serve.reload message type to the WebSocket protocol
  2. Add a server-side handler that calls the existing reloadPulledExtensions() and reloadTrustedCollectives() functions directly (cleaner than the signal path)
  3. Wire --server / --token into the CLI command using withRemoteOptions() / requestServerResponse()

The existing SIGHUP path would be kept for local hot-reload.

Alternatives

None meaningful — the SIGHUP approach is fundamentally local-only.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

8/5/2026, 3:02:48 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack728/5/2026, 1:24:37 AM

Sign in to post a ripple.