[P2] Chrome Application Template Configuration Invalid

[JoshuaAFerguson]

Severity: P2 - LOW (Non-blocking)
Component: Database / UI - My Applications
Page: /applications

Issue

Chrome application has invalid/missing template configuration. Attempting to launch shows error:

The application 'Chrome' does not have a valid template configuration
HTTP 400 error

Impact

• Cannot launch Chrome application from UI
• Other applications likely affected
• User confusion

Root Cause

Database: Chrome application has null or invalid template_id. Application not linked to valid template.

Fix Required

-- Check current state:
SELECT id, name, template_id FROM applications WHERE name = 'Chrome';
SELECT id, name FROM templates WHERE name LIKE '%chrome%';

-- Fix template_id (example):
UPDATE applications
SET template_id = (SELECT id FROM templates WHERE name = 'chromium-browser' LIMIT 1)
WHERE name = 'Chrome';

Prevention

• Add validation in admin UI when creating applications
• Require template selection, don't allow null
• Show warning if template_id is invalid

Testing

• Chrome application launches successfully
• All applications have valid template_id
• Application creation validates template
• Error message is clear if template missing

Effort: 30 minutes (database fix) + 2 hours (UI validation)
Priority: Can defer to v2.1
Source: .claude/reports/UI_BUG_FIXES_REQUIRED.md

[JoshuaAFerguson]

Status: Deferred to v2.1 per UI_BUG_FIXES_REQUIRED.md

Priority: P2 (Low Priority)

Recommendation from bug report:

"Fix: Update template in database or resync from repository"
"Severity: Low - template appears to still work, just has incorrect resource limits"

Decision: Per the comprehensive UI testing report, this is a data issue rather than a code bug. The template works correctly but has suboptimal resource limits configured.

Suggested Resolution:

1. Update template configuration in database
2. Or trigger repository resync to get corrected template
3. Consider adding template validation during sync process

Timeline: Deferred to v2.1 along with template repository verification work

Branch: claude/v2-builder (no changes for this issue)

[JoshuaAFerguson]

Closing — fixed by #260 (manifests/kubectl/default-apps-configmap.yaml now seeds the chrome-selkies template) and the addition of selkies/chrome-selkies.yaml in streamspace-templates#2. The Chrome template now points at ghcr.io/streamspace-dev/chrome-selkies (Selkies-native) instead of the broken linuxserver Chromium image.