Skip to content

An Orca runtime can reach its server by a pairing code held in an environment variable - #31

Merged
adamfortuna merged 1 commit into
mainfrom
orca-pairing-code
Nov 15, 2026
Merged

adamfortuna merged 1 commit into
mainfrom
orca-pairing-code

Conversation

@adamfortuna

Copy link
Copy Markdown
Contributor

An app in a container keeps no Orca pairing on disk, so orca environment add is no use to it.

A runtime's config can now name the environment variable that holds an Orca server's pairing code ("pairing_code_env": "ORCA_PAIRING_CODE", under Advanced on the runtime form). Harbor sends the code with every orca command (--pairing-code). The code is never stored in the runtime, shown on a page or put in an error. A runtime whose variable is empty takes no work and says which variable.

Not yet proven: checked against Orca 1.4.257's command line only, not run against a real remote server.

0.25.1.

…ironment variable

An app in a container keeps no Orca pairing on disk, so `orca environment
add` is no use to it. A runtime's config can now name the environment
variable that holds a server's pairing code ("pairing_code_env"), and
Harbor sends the code with every orca command (--pairing-code). The code
is never stored in the runtime, shown on a page or put in an error; a
runtime whose variable is empty takes no work and says which variable.

Checked against Orca 1.4.257's command line only. 0.25.1.
@adamfortuna
adamfortuna merged commit f3a4060 into main Nov 15, 2026
2 checks passed
@adamfortuna
adamfortuna deleted the orca-pairing-code branch November 15, 2026 00:36
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