Hi everyone, I'd like to share a bit about this project, which I've already tested and have experience developing.
First, I'd like to say that the panel should only be used outside of production. It's a product entirely focused on working outside of production. There are severe bugs in the system, and it should never be used in production.
1) The developer isn't focusing on stability; instead of fixing critical bugs, they're doing refactoring.
2) There are serious bugs, such as the TS/mpegts connection failing to close correctly over time, accumulating several active connections that have already been closed.
3) Constant changes that aren't focused on stability, like refactoring. In fact, I believe the developer is trying to make the project, which is without a framework, "LARAVEL-LIKE," creating a structure similar to Laravel but without using Laravel's specific features.
4) Again, since the updates aren't focused on stability, each update commonly causes bugs or completely breaks the service.
I participate in the development group, in addition to being an active donor.
I suggest the developer focus on stability instead of refactoring. I'll go further and say that the old structure before the Laravel-like refactoring was better. I suggest the developer consider reverting to the previous structure before the refactoring.
There are several other bugs, which are not worth highlighting here.
@Divarion_D
But the developers themselves say it's a beta product that shouldn't be used in production.