-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
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
add reference to env variables & tokens #177
base: master
Are you sure you want to change the base?
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
--- | ||
title: "Environment variables" | ||
linkTitle: "Environment variables" | ||
date: 2025-01-01 | ||
weight: 4 | ||
description: > | ||
Configure common environment variables | ||
|
||
--- | ||
|
||
This page lists some of the most common environment variables used in OpenCue. | ||
|
||
## Outline | ||
|
||
Environment variables related to pyOutline. | ||
|
||
### OL_BASE_SESSION_PATH | ||
|
||
|
||
### OL_LAYER_SESSION_PATH | ||
|
||
|
||
### OL_LAYER_RANGE | ||
|
||
|
||
### OL_VERSION | ||
|
||
|
||
### OL_OS | ||
|
||
|
||
### OL_TAG_OVERRIDE | ||
|
||
|
||
### OL_CONFIG | ||
|
||
## Cuebot | ||
|
||
Environment variables related to Cuebot. | ||
|
||
### CUEBOT_HOSTS | ||
|
||
|
||
### CUEBOT_GRPC_CUE_PORT | ||
|
||
|
||
### CUEBOT_GRPC_RQD_SERVER_PORT | ||
|
||
|
||
## Others | ||
|
||
|
||
### CUEGUI_DEFAULT_INI_PATH | ||
|
||
|
||
### OPENCUE_CONF | ||
|
||
|
||
### CUESUBMIT_CONFIG_FILE | ||
|
||
|
||
### CUE_FRAME_LOG_DIR | ||
|
||
|
||
### CUE_FS_ROOT | ||
|
||
|
||
### CUE_PYTHON_BIN | ||
|
||
|
||
### CUE_PYTHONPATH |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
title: "Tokens" | ||
linkTitle: "Tokens" | ||
date: 2020-04-03 | ||
weight: 5 | ||
description: > | ||
Various tokens that can be used in the commands you send to Cue | ||
--- | ||
|
||
Tokens can be used in the commands when submitting outline jobs, either in the graphical Cuesubmit client, or via the PyOutline API. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please break up long lines of text to avoid wrapping. I usually use a 100-char limit on lines. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. please review the PR now. |
||
|
||
Following are the commonly used tokens: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I recommend updating to: This page describes tokens you can use in commands when submitting OpenCue jobs, either in the graphical Cuesubmit (I would delete the sentence 'Following are the commonly used tokens:' as we're not |
||
|
||
##### #ZFRAME# | ||
The frame number zero-padded to four places. | ||
|
||
##### #IFRAME# | ||
The number of the current frame. | ||
|
||
##### #FRAME_START# | ||
The number of the final frame in the current chunk. | ||
|
||
##### #FRAME_END# | ||
The number of the final frame in the current chunk. | ||
|
||
##### #FRAME_CHUNK# | ||
The value of the current chunk. | ||
|
||
##### #LAYER# | ||
The name of the current layer. | ||
|
||
##### #JOB# | ||
The name of the current job. | ||
|
||
##### #FRAMESPEC# | ||
The value of the current frame spec. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend updating the description to:
Specify dynamic tokens in OpenCue jobs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, here I'm just describing the value of the string to update. I'm not describing the syntax or the way you should update the code. If you looks at similar Markdown (
.md
) files, you should be able to work out how to format the description but let us know if you're stuck.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh ya, sorry my bad. I didn't pay attention to that.
Will fix this