Centrifugo
sail
Our great sponsors
Centrifugo | sail | |
---|---|---|
31 | 9 | |
7,914 | 1,558 | |
2.4% | 2.6% | |
9.0 | 8.4 | |
5 days ago | about 1 month ago | |
Go | Shell | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Centrifugo
-
WebSockets vs. Server-Sent-Events vs. Long-Polling vs. WebRTC vs. WebTransport
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.
- Centrifugo v5.1.0 released, with new powers for real-time messaging tasks, now with proxy GRPC subscription streams – similar to WebSocketd but over the network
-
Integrating websockets into my current app
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.
- Millions of Active WebSockets with Node.js
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
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.
-
Laravel Websockets vs Soketi vs Laravel Echo Server
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:
-
Is Python a good option to implement Websockets?
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 – real-time messaging server (WebSocket, etc.) which scales well and integrates with any backend. SDKs for browser and mobile development included
-
What is the coolest Go open source projects you have seen?
Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo
- Golang updating the front-end with almost real-time events from the backend server
sail
- Laravel Sail add support for Bun
-
⛵ Laravel Sail - Windows 10 Installation
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.
-
You might wondering why Laravel Sail always has 0 open issue. answer: "That guy" always close unresolved issues with unhelpful comment.
If this is your issue I can totally understand why it's closed. https://github.com/laravel/sail/issues/470
-
Laravel docker
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.
-
Issue with Laravel Sail on Windows11 + WSL2
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
-
How To Update Laravel Sail To PHP v8.1
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.
-
Should I move to Docker?
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
-
Just another simple, fast, and resilient open-source WebSockets server. 📣
If it supports Docker, it can be installed in Laravel Sail (I have already submitted a PR for this)
-
Please help with Laravel/Sail/Phpstorm/XDebug
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
What are some alternatives?
Socket.io - Realtime application framework (Node.JS server)
Laradock - Full PHP development environment for Docker.
NATS - Golang client for NATS, the cloud native messaging system.
docker-compose-laravel - A docker-compose workflow for local Laravel development
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
lando - A development tool for all your projects that is fast, easy, powerful and liberating
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
docker-laravel-echo-server - Repository of oanhnn/laravel-echo-server Docker image.
laravel-websockets - Websockets for Laravel. Done right.
devilbox - A modern Docker LAMP stack and MEAN stack for local development
soketi - Next-gen, Pusher-compatible, open-source WebSockets server. Simple, fast, and resilient. 📣