Lightning TV Live
Changelog
A plain-English history of improvements to the viewing and match-night experience.
Current version
v1.4.0
-
- Operations teams have dry-run-first tools for encrypted PostgreSQL backups, isolated restore verification, and controlled application-image rollback.
- A concurrent viewer and operator load harness, dependency-outage drills, and a match-night incident runbook make capacity and recovery checks repeatable in a safe staging environment.
- Release metadata, changelog revisions, application versions, migrations, operational artifacts, and the full test suite are now checked automatically before deployment.
- Browser, device, accessibility, slow-network, handover, and two full-match rehearsal templates clearly record what was tested and keep unrun external checks visible instead of treating them as passed.
-
- Match-night changes now have a protected, chronological audit history showing their source, staff member, reason, and before-and-after values without storing credentials.
- Operators can preview score and event corrections before applying them, while withdrawals, replacements, and conflicting edits remain traceable instead of deleting the original record.
- Post-game reconciliation compares the scoreboard, GameStats, and reviewed local events, then keeps critical differences open until a staff member resolves or explicitly accepts them.
- A close-game checklist prevents unfinished review or replay work from being overlooked, records any later reopening, and provides deterministic per-game and season CSV or JSON exports.
-
- Operators can see live health for scoreboard feeds, GameStats, WebSockets, replay processing, Redis and clip storage, with clear warnings and recovery advice when something needs attention.
- A safe manual mode keeps the public scoreboard running during feed outages, records who changed each value, and holds returning OCR differences for review before automatic updates resume.
- Shot, faceoff and stoppage replay jobs can be reviewed together and safely retried, cancelled or re-extracted without losing their original clip window.
- Viewers receive a discreet notice when live data is under operator control or being checked after an outage.
-
- Purchasers with an existing account are now taken straight to a pre-filled sign-in screen, while new purchasers see account creation first.
- Account screens clearly explain which action is needed and keep alternative sign-in or registration links available without distracting from the main step.
- Viewers who have forgotten their password can request a secure reset link and choose a new password before signing in.
-
- Match stoppages can now be captured from the live event feed and sent through a dedicated review workflow.
- Reviewers can inspect replay clips, correct the stoppage reason, and safely retry failed exports.
- Operators have clearer queue states and controls for handling stoppages during a broadcast.
-
- The scoreboard now presents active penalties, team penalty minutes, team branding, and reviewed game statistics in one place.
- Timeline events from the external game feed are combined with locally reviewed events so supporters see a more complete account of the game.
- The scoreboard becomes a compact, sticky panel while scrolling and moves smoothly between its full and compact layouts.
- Team logos are delivered through a reliable application endpoint, with management controls available to administrators.
- Login and account confirmation screens have been refined for better clarity on both desktop and mobile devices.
-
- Faceoff maps can be filtered more precisely and now include clearer summary statistics.
- Player-level faceoff performance makes it easier to understand who is succeeding in each area of the ice.
- The deployment workflow now includes the documented Portainer redeployment step used by the production service.
-
- Shot and faceoff reviews share a clearer queue, giving specialist reviewers one place to find outstanding work.
- Faceoff timing is more stable when a scoreboard feed only reports values that have changed.
- Failed replay clips can be retried without recreating the original event.
- Penalty events are synchronised with the match feed, and approved clips can be opened from public game pages.
- Team styling and review validation were simplified to prevent stale or conflicting match data.
-
- Game lists now include filters, pagination, and consistent navigation between match tools.
- Live game handling and engagement controls have been tightened for busy match-night use.
- Scoreboard ingest, vMix worker, Docker, and Portainer settings are documented and configurable for different venues.
-
- Replay exports use fixed clip windows and stronger processing safeguards so clips are more consistent.
- Approved supporter messages can be delivered to the vMix social feed with clearer delivery status for moderators.
- Viewer watermarks, responsive data tables, and safer environment-file handling improve the public and operational experience.
- A live replay operations guide was added for match-night teams.
-
- Faceoff tracking, goal judging, shot review, and basic analytics were added for the match-night team.
- Administrators can import games and manage site-wide operational settings.
- Role-focused screens keep sensitive controls away from general viewer accounts.
-
- Scores and match activity can update in the browser in real time without refreshing the page.
- Supporters can take part in polls, predictions, trivia, and moderated fan messaging.
- Operators gained a live control area for match events and audience engagement.
- The first container build workflow made repeatable deployments possible.
-
- Supporters can register, sign in, and use a stream code to reach the games available to them.
- The first match models and game pages established the core viewing experience.
- Form validation provides clear feedback when account details or access codes cannot be accepted.
-
- The Lightning TV web application, database structure, and administration area were established.
- Initial support for games, user accounts, and controlled stream access was put in place.
- Automated checks were introduced for the earliest access-code journeys.
