Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
Silo Kody — review completeReview finished. Check the inline comments for findings and verify each suggestion against the code and tests. Reviewing changes in Silo
Review settingsReview OptionsThe following review options are enabled or disabled:
|
|
Draft until Silo-Server/silo-server#4668 and Silo-Server/silo-server#4665, which it's stacked on, are merged into main. The docs describe that change, and its labels or defaults may still change in review. |
|
|
||
| ## Connect providers from your deployment | ||
|
|
||
| To connect providers from a Compose file, Kubernetes manifest, or NixOS configuration instead, list them under `ai_providers` in the [deployment document](/docs/provision-plugins#connect-ai-providers). A provider the document declares opens read-only under **Providers**, with a note such as **Set by SILO_CONFIG_FILE in the server's environment.** It has no **Save** or **Remove**, and **Test** still works. To change or remove it, edit the document and restart Silo. Under **Models**, choose it for the **Text model** or **Speech-to-text** as you would any other provider. |
There was a problem hiding this comment.
Removing a provider from the document does not disconnect it
The provider remains connected and usable after its document entry is removed. Tell administrators to remove the entry, restart Silo, and then remove the provider under Providers.
Prompt for LLM
File src/content/docs/docs/running-a-server/ai-services.md, line 38:
Removing a provider from the document does not disconnect it
Removing a provider from the document only releases ownership; it remains connected and usable, contrary to the instruction here. Tell administrators to remove the entry, restart Silo, and then remove the provider in the admin pages.
Suggested code:
To change it, edit the document and restart Silo. To remove it, remove its entry from the document, restart Silo, and then remove the provider under **Providers**.
Talk to Kody by mentioning @kody
Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.
|
Preview deployed: https://pr-446.siloserver-org.pages.dev
Docs changes: 15 changes on 3 pages. Each link opens the first change on its page. Step through the rest with the changes box in the corner of the preview.
The alias updates after a successful build and deployment. The preview is removed when this pull request closes. |
- A declaration keeps a connected provider's type, replaces it whole, and shares the document's secret limit with plugin secrets. - State the id rule and that custom providers need capabilities, and use a generic host in the custom example. - Show the AI key's secret in the Compose, Kubernetes and NixOS steps. - Keep the read-only provider description on AI Services, say that removing the document releases nothing, and how to remove a released provider. - Split the recommendations variables paragraph, say where to set them and which provider ids work, and cover switching a provider the environment sets. - Keywords: drop words the page already uses.
Silo Kody — review completeReview finished. Check the inline comments for findings and verify each suggestion against the code and tests. Reviewing changes in Silo
Review settingsReview OptionsThe following review options are enabled or disabled:
|
Silo Kody — review completeReview finished. Check the inline comments for findings and verify each suggestion against the code and tests. Reviewing changes in Silo
Review settingsReview OptionsThe following review options are enabled or disabled:
|
Problem
Closes #445
The plugin provisioning document is now Silo's deployment document. Besides plugins, it can connect AI providers, and three new variables set up recommendations, so a Compose, Kubernetes, or NixOS deployment can configure AI services without the admin pages. The docs covered only plugins under the old variable names.
Draft until Silo-Server/silo-server#4668 and the pull request it's stacked on, Silo-Server/silo-server#4665, are merged into main. The docs describe #4668, and its labels or defaults may still change in review.
Pages changed
SILO_CONFIG_FILESILO_RECOMMENDATIONS_*variables under "Configure the model"; changing the model when the variables set itWhat changed on each page
Configure Silo from a deployment document
docs/provision-plugins, so existing links keep working.SILO_CONFIG_FILE(YAML or JSON file) andSILO_CONFIG(inline JSON), with "The older names,SILO_PLUGINS_FILEandSILO_PLUGINS, still work and read the same document. Set only one of the four: if two are set, Silo doesn't start." Bothpluginsandai_providersare optional, and a section left out leaves those plugins or providers as they are. A short pointer sends AI-only readers to the new section, and the OIDC walkthrough gets its own subheading.customendpoint, the id rule (1 to 64 lowercase letters, digits, and hyphens, starting with a letter or digit),typevalues and defaults,api_keyonly asfromFileorfromEnv(with the four types that need one),capabilitiesrequired forcustomand refused for the rest, the name-clash stop and its two fixes, replacing a stored provider with the same id and type (a type change stops startup), an example startup error, a pointer to the read-only view on AI Services, and the last-to-start-wins rule. Plugin secrets and AI keys share one 1 MiB secret limit.SILO_CONFIG_FILEand adeployment.yamlordeployment.jsonfile, and show the AI key's secret next to the OIDC one.plugins: {}releases every plugin, and leaving the section out releases nothing. New bullet forai_providers, with the same rules forai_providers: {}and for leaving the section out, and that removing the document releases nothing; a released provider can be removed once no job uses it.Worth checking: I kept the heading "Prepare the declaration" so its anchor doesn't change.
Configure AI services
Set up recommendations
SILO_RECOMMENDATIONS_ENABLED,SILO_RECOMMENDATIONS_PROVIDER(the id of a provider the document declares; admin-added providers' ids aren't shown) andSILO_RECOMMENDATIONS_MODELset Enable Recommendations, Embedding provider, and Model, which then show read-only while Check Connection still works. A second paragraph: they apply on the start that reads them, the startup error for a provider that isn't connected, and the last-to-start-wins rule.Left out on purpose
configuration.md.managed_by_env_varfield and the422managed_by_environmentrefusal: no other page goes to API level.Evidence
Source reviewed, not tested on a live server or device:
silo-server
de5b0fd907(Silo-Server/silo-server#4668 with its review fixes), stacked onc7622a0b58(Silo-Server/silo-server#4665). Docs branch from siloserver.orgd3b0482.The server PR's own evidence shows the read-only provider panel and Recommendations fields on a running server with a declared provider; these pages weren't checked against one separately.
Evidence: https://evidence.siloserver.org/r/siloserver-org/deployment-ai-providers/
Follow-ups
SILO_CONFIG,SILO_CONFIG_FILE, and the threeSILO_RECOMMENDATIONS_*variables to the table, and update its link text "Provision plugins from deployment configuration" to the new page title.Risks
None identified. Documentation only.
Checklist
AI Disclosure
🤖 Generated with Claude Code