Added the Manual Installation deadline[gui] section #943
Conversation
github-actions
bot
added
the
waiting-on-maintainers
skarpree
force-pushed
the
manual_deadline-gui]_instruction
branch
2 times, most recently
from
c8c68b0 to
6c29bf7
Compare
docs/index.md
Outdated
|
|
||
| Install the packages into the appropriate Submitter or Python environment where the Deadline Client is installed: | ||
| ``` | ||
| /Path/to/python -m pip install --no-index --upgrade --find-links /your/pypi/bundle/from/above --target /Your/Target/python/module/dir *.whl |
There was a problem hiding this comment.
This is quite hard to understand, what is /your/pypi/bundle/from/above, and what is /YourTarget/python (different case?)
Can you provide more details what the args do?
There was a problem hiding this comment.
+1, hard to follow. Maybe add a step to check the bundle from the above step so the flow to this command makes sense and is easy to follow
leongdl
added
response-requested
docs/index.md
Outdated
|
|
||
| Use the Python version bundled with the installer to download the Deadline GUI components using pip: | ||
| ``` | ||
| /Path/to/python -m pip download -d /your/download/directory deadline[gui]=={DEADLINE_CLIENT_VERSION} |
There was a problem hiding this comment.
I think we should keep the path examples consistent. For eg. path/to/python and path/to/your/download/directory. Also avoid the / at the beginning to avoid confusion
docs/index.md
Outdated
|
|
||
| Install the packages into the appropriate Submitter or Python environment where the Deadline Client is installed: | ||
| ``` | ||
| /Path/to/python -m pip install --no-index --upgrade --find-links /your/pypi/bundle/from/above --target /Your/Target/python/module/dir *.whl |
There was a problem hiding this comment.
+1, hard to follow. Maybe add a step to check the bundle from the above step so the flow to this command makes sense and is easy to follow
github-actions
bot
added
waiting-on-maintainers
Signed-off-by: skarpree <[email protected]>
Signed-off-by: client-software-ci <[email protected]> Signed-off-by: Eric Osiowy <[email protected]> Signed-off-by: skarpree <[email protected]>
Updated the instructions to be more clear for the customer to follow. Signed-off-by: skarpree <[email protected]>
skarpree
force-pushed
the
manual_deadline-gui]_instruction
branch
from
4a2f375 to
3cc8008
Compare
|
|
|
||
| Use the Python version bundled with the installer to download the Deadline GUI components: | ||
| ```bash | ||
| path/to/python -m pip download -d path/to/download/directory deadline[gui]=={DEADLINE_CLIENT_VERSION} |
There was a problem hiding this comment.
One nit - I think we need to mention the same python package is needed on both machines?
| * The CLI `bundle gui-submit --submitter-name` option has been deprecated. `--submitter-info` should now be used to provide the name. | ||
| ## 0.54.0 (2025-12-09) | ||
|
|
||
| ### BREAKING CHANGES |
There was a problem hiding this comment.
This seems odd your PR changed the change log?
There was a problem hiding this comment.
I think this came from the 0.54 deadline release chore commit. Branch needs to be rebased
moorec-aws
added
response-requested
5 participants
What was the problem/requirement? (What/Why)
The documentation was missing instructions for offline installation of Deadline Client GUI components. Users working in air-gapped or restricted network environments need guidance on how to download and install these components without direct internet access.
What was the solution? (How)
Added new offline installation instructions that include:
What is the impact of this change?
Users in offline or restricted network environments can now successfully install Deadline Client GUI components by following the documented procedure. This expands the accessibility of the product to air-gapped deployment scenarios.
How was this change tested?
Was this change documented?
Does this PR introduce new dependencies?
Is this a breaking change?
No, this is a documentation-only addition with no impact on code functionality or public contracts.
Does this change impact security?
No, this change only adds documentation content. No security implications.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.