We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Covers the linux part of: #527
The linux configuration.sh both create scripts that use --server-comms-port "10943" without allowing for --server-comms-address to be specified and so can not support https://octopus.com/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443#registering-a-new-tentacle
The text was updated successfully, but these errors were encountered:
The linux configure-tentacle.sh script now supports setting comms por…
2ee6d71
…ts other than 10943. (#792) * Support non 10943 comms ports in the linux tentacle config script * Support a different address Fixes: #793
Release Note: configure-tentacle.sh now supports configuring the comms address and port.
Sorry, something went wrong.
LukeButters
Successfully merging a pull request may close this issue.
Covers the linux part of: #527
The linux configuration.sh both create scripts that use --server-comms-port "10943" without allowing for --server-comms-address to be specified and so can not support https://octopus.com/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443#registering-a-new-tentacle
The text was updated successfully, but these errors were encountered: