1.7 KiB
Our story
The story behind Vyla, from a small web project to a self-hosted ecosystem.
Vyla started from a web project that initially intended to create a clean environment where one could stream movies and TV shows free from all the unnecessary elements. Originally, it was developed mainly as a frontend which embedded other players. With time, I got involved in the process of developing the infrastructure.
Another core component of Vyla is Vyla API, which dealt with searching streams from various providers, verifying their availability, and playing them. Later on, it evolved into being able to cope with many kinds of streams and deal with possible issues related to their quality and reliability.
With constant changing and breakage of providers, I had to develop Vyla SDK. The purpose of it was to isolate the source implementations from the rest of Vyla so that they could be independently managed and used in other projects. I made each source into provider modules which had the same interface. Vyla SDK remains updated as sources change.
Among the main challenges associated with the development of Vyla was hosting. Initially, I did self-hosting of the frontend, API, player, Nginx, PM2, and other infrastructure on a VPS. Managing them was a struggle with constant downtime, provider issues, Cloudflare problems, and, lastly, DMCA complaints.
However, after receiving a DMCA strike and experiencing problems due to frequent reports in Cloudflare, I figured out that it wouldn't be efficient to self-host the streaming infrastructure. Therefore, the choice was made to focus more on the SDK and the applications rather than using a remote backend.
Thanks for reading ❤️