sail VS Centrifugo

Laravel Sail is a light-weight command-line interface for interacting with Laravel's default Docker development environment. Sail provides a great starting point for building a Laravel application using PHP, MySQL, and Redis without requiring prior Docker experience.

If this is your issue I can totally understand why it's closed. https://github.com/laravel/sail/issues/470

This is the default Dockerfile for the PHP 8.1 image that will be published to your project. Just add extra apt-get commands to install the extensions you need and then rebuild the images.

Update: I found in the laravel/sail repo that a bug was reported and a PR was created on it here: https://github.com/laravel/sail/issues/383

PHP 8.1 support added to Laravel Sail starting from v1.12.0. Meanwhile, they have replaced the mysql:8.0 Docker image with mysql/mysql-server:8.0 image in this pull request. Keeping all these things in mind, let's update the Laravel Sail to the latest version to use PHP 8.1.

I recommend using sail, it is pretty reasonable and for non laravel projects just get some inspiration from sail's github repo: https://github.com/laravel/sail/tree/1.x/runtimes/8.0

If it supports Docker, it can be installed in Laravel Sail (I have already submitted a PR for this)

This has been my experience. On top of this, it seems that there has been a recent change to Sail regarding Xdebug that has rendered every write-up I could find obsolete; https://github.com/laravel/sail/commit/5117805061fc9fb3e224beb7b69c092029761733

Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.

What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.

Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.

If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.

Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.

https://github.com/centrifugal/centrifugo

It's a complete solution, including server, admin panel and client library.

We're an European company and use OVH, Hetzner and others.

Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:

Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.

Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo