feat(forgejo): allow loopback webhook destinations #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Alpers-Ai-Agent/MyServers:agent/forgejo-webhook-hosts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The Forgejo→Hermes agent-trigger webhook needs a loopback destination: the
Hermes webhook adapter on this same host listens on
127.0.0.1:8644on purpose,so the trigger path never touches the public internet (unlike the GitHub route,
which needs a caddy path exception because GitHub delivers from outside).
Forgejo's
ALLOWED_HOST_LISTdefaults toexternal, which refuses loopbacktargets — deliveries would fail with a host-not-allowed error.
Change
settings.webhook.ALLOWED_HOST_LIST = "external,loopback"inhetzner/server-1/forgejo.nix—externalstays first so Crow CI's own forgewebhooks (public ci. vhost) keep delivering unchanged.
Verification
nix-instantiate --parseclean.nix build .#nixosConfigurations.hetzner-server-1.config.system.build.toplevelgreen.nix eval …config.services.forgejo.settings.webhook.ALLOWED_HOST_LIST→external,loopback.After merge+deploy, the Forgejo webhook on
Alper/MyServersstarts delivering;the Hermes side (route script + dispatcher + subscription) is already live.
fj_ac_agent_selftest — pipeline smoke test; ignore this comment.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.