There's an issue where the state of the dynamic backend is not reflected in the static frontend.
There could be 2 new vods that trigger a mux deletion of the previous 2, but the UI will not show that until the frontend is rebuilt.
Solution 1-- go dynamic. Populate vods using live data from the backend
Solution 2-- remain hybrid static/dynamic, using islands to show live status of mux assets
Solution 3-- ???
Solution 4-- Queue mux-asset deletions to occur at a later time. This is probably necessary no matter the solution. We don't want to have a situation where a mux-asset is deleted, and anybody watching that vod is suddenly cut off. I think there needs to be something like a 2 day lag between when a mux-asset is marked for deletion and when the deletion occurs. However, as soon as the deletion is queued, the update shows in the UI as soon as possible. Again, probably a live data island is the way to do this, since Fleek doesn't have a public API way of triggering builds.
Maybe it is best to use use Fleek for big UI updates, and use dynamic islands for changes to live data. This would eliminate the need for #180
There's an issue where the state of the dynamic backend is not reflected in the static frontend.
There could be 2 new vods that trigger a mux deletion of the previous 2, but the UI will not show that until the frontend is rebuilt.
Solution 1-- go dynamic. Populate vods using live data from the backend Solution 2-- remain hybrid static/dynamic, using islands to show live status of mux assets
Solution 3-- ???
Solution 4-- Queue mux-asset deletions to occur at a later time. This is probably necessary no matter the solution. We don't want to have a situation where a mux-asset is deleted, and anybody watching that vod is suddenly cut off. I think there needs to be something like a 2 day lag between when a mux-asset is marked for deletion and when the deletion occurs. However, as soon as the deletion is queued, the update shows in the UI as soon as possible. Again, probably a live data island is the way to do this, since Fleek doesn't have a public API way of triggering builds.
Maybe it is best to use use Fleek for big UI updates, and use dynamic islands for changes to live data. This would eliminate the need for #180