hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Add lightweight live UI refresh #36

New Issue
Closed
opened 2026-05-21 14:35:24 +02:00 by parkel · 0 comments
parkel commented 2026-05-21 14:35:24 +02:00
Owner
Copy Link

Goal

Introduce Django-friendly partial refresh behavior for operational pages so pobsync feels more like a live control panel without adopting a full frontend framework.

Suggested Approach

Prefer server-rendered partials with HTMX or small vanilla JavaScript. Avoid a React/Vue/Svelte build step unless a specific interaction genuinely requires it.

Scope

  • Evaluate adding HTMX for partial updates.
  • Add auto-refresh for the most valuable status surfaces first, such as dashboard activity, run detail status/log availability, and possibly log filters.
  • Keep pages usable without complex client-side state.
  • Avoid refreshing forms while a user is editing them.

Acceptance Criteria

  • At least one high-value status panel refreshes automatically without a full page reload.
  • The implementation remains Django-template-first and easy to maintain.
  • Refresh behavior is documented briefly for future UI work.
  • Tests cover the partial view or endpoint used for refreshes.
## Goal Introduce Django-friendly partial refresh behavior for operational pages so pobsync feels more like a live control panel without adopting a full frontend framework. ## Suggested Approach Prefer server-rendered partials with HTMX or small vanilla JavaScript. Avoid a React/Vue/Svelte build step unless a specific interaction genuinely requires it. ## Scope - Evaluate adding HTMX for partial updates. - Add auto-refresh for the most valuable status surfaces first, such as dashboard activity, run detail status/log availability, and possibly log filters. - Keep pages usable without complex client-side state. - Avoid refreshing forms while a user is editing them. ## Acceptance Criteria - At least one high-value status panel refreshes automatically without a full page reload. - The implementation remains Django-template-first and easy to maintain. - Refresh behavior is documented briefly for future UI work. - Tests cover the partial view or endpoint used for refreshes.
parkel added this to the 1.1 milestone 2026-05-21 14:35:24 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone 1.1
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?