feat: support configurable server bind host#8096
Merged
Merged
Conversation
snapss-dev
force-pushed
the
security/loopback-bind
branch
from
July 17, 2026 23:29
c63601a to
81c836b
Compare
This was referenced Jul 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CAMOFOX_BIND_HOSTconfigurationapp.listenWhy
Local-only deployments currently bind the API to every interface. This option lets operators explicitly bind to
127.0.0.1without changing cloud or container defaults.Verification
npm test -- --runInBand tests/unit/config.test.jspasses (3/3)CAMOFOX_BIND_HOST=127.0.0.1127.0.0.1:9377The full
npm testrun completed 40 suites with 668 passing tests; the E2E suites that require/tmp/camofox-e2e-env.jsonfailed because that shared environment was not started in this standalone checkout.