forge: FORGE_CONFIG env fallback for CLI --plugin mounts

melvincarvalho · melvincarvalho · commit 313d39fc5f8e · 2026-07-13T04:52:02.000+02:00
jspod / `jss --plugin module@prefix` mount a plugin with no per-plugin config
object (that's config-file territory). When the FORGE_CONFIG env var names a
JSON file, merge it into api.config as DEFAULTS at activate() — so a
CLI-mounted forge can still opt into Nostr announce relays, marks/chain,
openEdit, etc. Explicit api.config always wins; unset env or an unreadable
file is a silent no-op, so existing config-file deployments and the test
suite are unaffected (126 tests unchanged).
diff --git a/forge/plugin.js b/forge/plugin.js
@@ -863,6 +863,17 @@ async function findBackend(config) {
 
 export async function activate(api) {
   const prefix = api.prefix || '/forge';
+  // CLI --plugin mounts (jspod, `jss --plugin module@prefix`) pass no per-plugin
+  // config. When FORGE_CONFIG names a JSON file, merge it in as DEFAULTS so a
+  // CLI-mounted forge can still opt into Nostr/marks/etc. Explicit api.config
+  // wins; unset env or unreadable file is a silent no-op (behavior unchanged).
+  if (process.env.FORGE_CONFIG) {
+    try {
+      api.config = api.config || {};
+      const fc = JSON.parse(fs.readFileSync(process.env.FORGE_CONFIG, 'utf8'));
+      for (const k of Object.keys(fc)) if (api.config[k] === undefined) api.config[k] = fc[k];
+    } catch (e) { api.log?.warn?.(`forge: FORGE_CONFIG load failed: ${e.message}`); }
+  }
   const privateRepos = api.config.privateRepos ?? false;
   // Web-edit DEMO relaxation (tier 3.7): when true, the single-file edit
   // endpoint accepts ANONYMOUS edits (no owner signature). This is never a
