fix(server): warn instead of exit when FORGE_TOKEN/WEBROOT unset (0.4.5) #112

Closed

zaelgohary wants to merge 2 commits from development_fix_strict_startup_env into development

zaelgohary commented

2026-05-20 11:02:21 +00:00

Member

Summary

hero_proc_server no longer exits at startup when FORGE_TOKEN or WEBROOT are missing — it logs a warning and continues, with WEBROOT falling back to http://127.0.0.1:9998/. Lets deployments that don't use Forge package pulls run without dummy env values.

Closes #111.

Changes

Replaced strict exit checks with warn-only behaviour
Added default WEBROOT fallback
Bumped to 0.4.5

Test Results

Deployed to slides VM with FORGE_TOKEN removed; hero_proc restarted cleanly, /rpc system.ping HTTP 200.

## Summary hero_proc_server no longer exits at startup when `FORGE_TOKEN` or `WEBROOT` are missing — it logs a warning and continues, with `WEBROOT` falling back to `http://127.0.0.1:9998/`. Lets deployments that don't use Forge package pulls run without dummy env values. ## Related Issue Closes #111. ## Changes - Replaced strict exit checks with warn-only behaviour - Added default WEBROOT fallback - Bumped to 0.4.5 ## Test Results Deployed to slides VM with FORGE_TOKEN removed; hero_proc restarted cleanly, /rpc system.ping HTTP 200.

zaelgohary added 2 commits

2026-05-20 11:02:21 +00:00

Make WEBROOT optional with default fallback ddb135bf8d

Remove the WEBROOT environment variable check that required it to be
set at startup. Instead, provide a sensible default value of
http://127.0.0.1:9998/ when the variable is not set.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>