Skip to content

Support specifying host to bind to in config - #37

Open
DarkOtter wants to merge 1 commit into
bitburner-official:mainfrom
DarkOtter:allow-configuring-hostname
Open

Support specifying host to bind to in config#37
DarkOtter wants to merge 1 commit into
bitburner-official:mainfrom
DarkOtter:allow-configuring-hostname

Conversation

@DarkOtter

Copy link
Copy Markdown

This should allow running listening only on localhost for better security when bitburner and the sync are both run on the same host, which I imagine is common.

Ran tests for commit:
npm run format
npm run lint
npm run test

(all tests passed)

Ran the program with unchanged config (no host specified), observed still listening on [::], observed able to connect and sync from bitburner on another host.

Added the host option set to localhost, ran again and observed I was unable to connect from the other host.

AI use: I asked AI for advice to save figuring out some project details myself, but all of the code changes were written myself.

This should allow running listening only on localhost for better security when bitburner and the sync are both run on the same host, which I imagine is common.

Ran tests for commit:
npm run format
npm run lint
npm run test

(all tests passed)

Ran the program with unchanged config (no host specified), observed still listening on [::], observed able to connect and sync from bitburner on another host.

Added the host option set to localhost, ran again and observed I was unable to connect from the other host.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant