admin: Lock runners to system Blender (override render settings)

s1d3sw1ped commented

2026-09-17 08:34:04 +00:00

Owner

we should add a feature where the runners can be locked to using the system blender instead or the one specified in the render settings and gathered from the manager this should be admin configurable not render settings also the render settings should be hidden when its being overridden

eva was assigned by s1d3sw1ped

2026-09-17 08:34:16 +00:00

s1d3sw1ped added the

Kind/Enhancement

label

2026-09-17 08:34:35 +00:00

eva changed title from ~~Proposal: lock to system blender configurable option~~ to admin: Lock runners to system Blender (override render settings)

2026-09-17 08:42:58 +00:00

eva removed their assignment

2026-09-17 08:42:58 +00:00

eva commented

2026-09-17 08:42:58 +00:00

Owner

Triage (Eva)

Justin proposal accepted as product work. Scope for the implementer:

Behavior

Admin-configurable option (not per-job render settings) to lock runners to the system Blender (PATH / detected system binary) instead of the Blender path from render settings / manager gather.
When the lock is on, runners must use that system binary; manager/render settings Blender choice is ignored for execution.
When the lock is on, hide (or clearly disable) the render-settings Blender picker / related UI so operators are not misled.
When the lock is off, existing render-settings Blender behavior stays.

Likely touchpoints

internal/manager/ (admin config persist + API), web/static/admin.js (+ any render settings UI), runner job path resolution (internal/runner/blender/, tasks/render.go).

Acceptance

Admin can toggle lock; setting survives restart.
Lock on → runner uses system Blender; render-settings Blender UI hidden/disabled.
Lock off → prior behavior.
Tests for config + path resolution.
One PR → default branch; admin: … / runner: …; Closes #13; do not merge yourself (Linus/Eva review).
Nontrivial: poteto-mode bar — prove with tests before claiming done; land via jumpbox Gitea (not CloudAgent).

## Triage (Eva) Justin proposal accepted as product work. Scope for the implementer: ### Behavior 1. **Admin-configurable** option (not per-job render settings) to lock runners to the **system Blender** (PATH / detected system binary) instead of the Blender path from render settings / manager gather. 2. When the lock is on, runners must use that system binary; manager/render settings Blender choice is ignored for execution. 3. When the lock is on, **hide** (or clearly disable) the render-settings Blender picker / related UI so operators are not misled. 4. When the lock is off, existing render-settings Blender behavior stays. ### Likely touchpoints - `internal/manager/` (admin config persist + API), `web/static/admin.js` (+ any render settings UI), runner job path resolution (`internal/runner/blender/`, `tasks/render.go`). ### Acceptance - Admin can toggle lock; setting survives restart. - Lock on → runner uses system Blender; render-settings Blender UI hidden/disabled. - Lock off → prior behavior. - Tests for config + path resolution. - One PR → default branch; `admin: …` / `runner: …`; `Closes #13`; do not merge yourself (Linus/Eva review). - Nontrivial: poteto-mode bar — prove with tests before claiming done; land via jumpbox Gitea (not CloudAgent).