truenas_ws: Add ability to deploy to remote TrueNAS server via WebSockets #6424
Conversation
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
rglidden
changed the title
rglidden
force-pushed
the
truenas_ws_remote
branch
from
ffa9271 to
6d40ac8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add support for deploying to remote TrueNAS instances via WebSockets by adding support for the
DEPLOY_TRUENAS_HOSTNAMEandDEPLOY_TRUENAS_PROTOCOLoptions that were already mentioned in the script but not implemented. Defaults tows://localhostto match the existing behaviour if the options are not supplied.Increased UI restart delay to 15 seconds to give the UI a little more time to restart.
Tested on TrueNAS Scale 24.10.2.2 and 25.04.1