Open zcesur opened 2 months ago
/bounty $50
/attempt #78
with your implementation plan/claim #78
in the PR body to claim the bountyThank you for contributing to algora-io/tv!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🔴 @aybanda | Sep 5, 2024, 6:04:09 AM | WIP |
🟢 @destinedcodes | Sep 12, 2024, 4:36:40 PM | WIP |
🟢 @vishwamartur | Nov 17, 2024, 5:19:09 PM | #119 |
@zcesur /attempt #78 Here is my implementation plan 1.Set up environment 2.Implement livestream status check 3.Implement old machine destruction check 4.Create livestream control endpoints 5.Test livestream start 6.Set up Fly.io deployment 7.Implement deployment monitoring 8.Run full demo deployment 9.Error handling
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@aybanda | 1 bounty from 1 project | Cancel attempt |
/attempt #78
Just checking in, is this still needed?
Yep, still open @raphaelbernhart
/attempt #78
💡 @vishwamartur submitted a pull request that claims the bounty. You can visit your bounty board to reward.
Let's set up a Fly.io deployment pipeline such that machines running with an old version are shut down gracefully. This is important to ensure livestreams are not interrupted during deployments
This tweet along with this complementary repo explain how we can implement this
The only missing part is to destroy old machines after all running livestreams are terminated, which we can implement inside the
end_of_stream
callback usingMembrane.Pipeline.list_pipelines
If anyone wants to tackle this, please include a short demo of the entire process in the PR, which should include: