Select an Installed Composition in DocsFab
An installed composition supplies a recorded model, serving route, transport,
and credential family. A public installation omits private endpoint defaults.
Select a composition with docsfab setup --profile instead of copying its YAML
MODEL_* fields.
Prerequisites
- Install DocsFab and obtain the key required by the composition’s provider.
- Refer to Execution Compositions for the installed records and their qualification status. Selecting an installed composition does not establish technical approval.
- Obtain the provider’s base endpoint URL when your installation omits that route’s default. Public installations require this for NVIDIA Inference Hub compositions. The API key alone does not configure an endpoint.
Steps
-
List the installed compositions and choose an active ID.
-
If the route has no installed endpoint default, export the provider’s base endpoint URL before selecting the composition:
Replace the example URL with your provider’s actual endpoint. Keep this variable exported for later commands, or save the endpoint in
host.yamlas described below. Do not put an API key in the URL. -
Select that ID and provide the key that setup requests.
Replace
COMPOSITION_IDwith the ID from the list. Setup skips the model and endpoint prompts; it does not discover a missing private endpoint. It writesactiveExecutionProfileandcompositionIdinhost.yamland names the required secret keys insecrets.env. It does not copy a YAML field block or save an exported endpoint inhost.yaml. -
To keep the endpoint after closing your shell, add
baseUrlunderactive.writing.settingsin your configuration root’shost.yaml:Merge these fields into the existing file, preserving its other settings. Replace the composition ID and example URL with your selected values. Keep credentials in
secrets.env. Environment variables override host settings; refer to Model Setting Precedence. -
Inspect the saved selection without calling the model:
profile inspectreports the standinghost.yamlconfiguration. Confirm that the summary names your selected model, provider, and configured limits. Afterdocsfab setup --profile <compositionId>, it also reportsBound execution profile:with that ID. By default,profile inspectdoes not contact the provider. Add--catalogonly when you want read-only provider catalog discovery. A ready local configuration does not verify that a remote endpoint accepts the key or supports the selected model.