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

Relationships

#1113 Docs: document --hot-reload flag and swamp serve reload subcommand

Opened by stack72 · 7/13/2026· Shipped 7/13/2026

Context

PR swamp-club/swamp#1826 adds opt-in SIGHUP-based hot-reload to swamp serve (fixing swamp-club#1089). The user-facing manual in swamp-club/swamp-club needs corresponding updates.

Changes needed

1. serve-flags.md — add --hot-reload to the flags table

Add a row to content/manual/reference/swamp-serve/serve-flags.md:

| --hot-reload | (off) | Enable SIGHUP-based hot-reload for pulled extension bundles. Writes a PID file to .swamp/serve.pid; use swamp serve reload to trigger |

2. New reference page: hot-reload.md

Create content/manual/reference/swamp-serve/hot-reload.md documenting:

  • The swamp serve reload subcommand (reads PID file, sends SIGHUP)
  • The hot-reload mechanism (per-type invalidation, ?fp= cache busting)
  • The user flow: start with --hot-reload, pull extension, run swamp serve reload
  • Limitations: SIGHUP not available on Windows, reloads all pulled extensions (no targeting), V8 module cache busting via fingerprint

3. Optional how-to guide

Consider a short how-to at content/manual/how-to/swamp-serve/reload-extensions-without-restart.md covering the three-step workflow:

  1. swamp serve --hot-reload
  2. swamp extension pull @name --force
  3. swamp serve reload
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 4 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

7/13/2026, 4:28:29 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack727/13/2026, 4:07:13 PM

Sign in to post a ripple.