Hunter Beast

If we're deployed on Modulus for production, we shouldn't bring down our entire API for minutes every time we re-deploy. This is a critical feature.

That's appreciated, thanks... We just went into production this morning, so... I'm really not sure if I'm comfortable having API downtime on each deployment, especially when working with CI.

I think a requirement should be that it's web-based so that it can be accessed by users of Umbrel and Start9 nodes. For a UI framework, I can recommend [Leptos](https://leptos.dev/)

Ooh, this ought to be good! I'm looking forward to seeing the solution. Will it be using bp-node, or something else?

LFG! :rocket:

So, wait, what are specifically supposed to do? I keep running into brick walls. Since I'm not able to split the Sink, I tried the WebSocketConnection inside a Mutex, but...

That's incredibly unnecessary, Rube-Goldbergian nonsense. We can just add the trait. It's not even a breaking change. Why does this have to be so difficult?

Alright, I've taken a walk and settled down a bit. I'm fine with maintaining the alternate library. Also, if you look at the code I was replacing in the link...

I think it's best to not overthink it. Since you have preview, it can be double-checked beforehand, at least.

I don't have an Umbrel, but I can package it up for Embassy once there's a UI. Ideally there'd also be a Dockerfile also, I think.