Skip to content

[Docs] Clarify Blaxel worker image configuration - #3256

Draft
roomote-community[bot] wants to merge 1 commit into
developfrom
fix/blaxel-docs-297z3jkrtk5wf
Draft

roomote-community[bot] wants to merge 1 commit into
developfrom
fix/blaxel-docs-297z3jkrtk5wf

Conversation

@roomote-community

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

  • documented the required BLAXEL_IMAGE value alongside the Blaxel API key and workspace for environment-based configuration
  • clarified when Roomote provisions and saves the worker image automatically and when operators must provision it separately

Why this change was made

The comprehensive public-documentation audit found that the Blaxel guide omitted a runtime-required value. The controller and compute-provider factory both require BLAXEL_IMAGE, while setup can populate it only when it can resolve a registry-qualified worker image.

Impact

Self-hosted operators now have complete Blaxel configuration guidance and can distinguish the automatic setup path from the manual fallback. No product behavior changes.

@roomote-community

roomote-community Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor Author

No code issues found. See task

Reviewed 9f245a7

This branch has not been deployed

No deployments
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