Download the PHP package werkraum/websocket-provider without Composer

websocket_provider

Provides basic setup to run Ratchet WebSocket servers within TYPO3.

Currently only for *nix Systems

composer req werkraum/websocket-provider

typo3cms websocket:start

Routes and Components

Components

Implement the Ratchet interface Ratchet\MessageComponentInterface in your extension. This is going to be the entry point for your logic.

Mark your component as public to make use of the Symfony dependency injection within it. Tag your component with websocket.component to register it with the WebSocket provider.

Configuration/Services.yaml

Routes

Symfony Routes are used to provide multi-tenancy.

You may let your component implement the interface CustomRouteInterface. Return your custom route path with a leading slash (e.g. /socket.io/my_component).

The default route for Vendor\Extension\MyComponent is /Vendor_Extension_MyComponent

Be aware that the route of your WebSockets may be prefixed by whatever you have set for your webserver config. In my case this is often /socket.io. You can set this server-wide prefix in the settings. The prefix is then prepended to every component route, even third-party ones using this extension.

The Loop

In case you need periodic timer or want to handle signals you can implement the interface ConfigureLoopInterface. You'll get the loop as parameter. The signals SIGTERM and SIGINT are already registered to shut down the server.

Configuration

See ext_conf_template.txt for all configuration options.

Commands

Demo

Ratchet ships a simple echo component. You can register it via Symfony DI.

any Configuration/Services.yaml

Security

Authentication

The current frontend and backend user sessions are added to the connection as UserAspects. The ID of the connection is added as well.

Connections are not rejected when not authenticated. Additionally the authentication is only checked on opening a connection.

Rate limiting

A basic limiter is shipped and can be configured in the settings. More sophisticated rate limiting should probably be done by your webserver.

Server config

ext-json, ext-pcntl and ext-posix are required for the cli commands to check on the status of the server.

NGINX

Laravel has some good documentation on how to setup NGINX for WebSockets.

https://beyondco.de/docs/laravel-websockets/basic-usage/ssl#usage-with-a-reverse-proxy-like-nginx

DDEV

Open the port. Either via DDEV config web_extra_exposed_ports or a custom docker-compose file.

docker-compose.websockets.yaml

Port and the URL part /socket.io can be adjusted to your needs. I recommend setting the extension setting route_prefix to whatever you set as the URL part in your websocket config.

Below is the proxy pass config that needs to be added to the webserver config. This uses a custom URL part to distinguish between WebSocket and regular HTTP requests. This integrates well with existing webserver configuration for TYPO3. The Laravel documentation has a Nginx setup without the URL part.

Remember to remove the #ddev-generated line in the webserver config otherwise your changes will be overridden after restarting DDEV.

Apache

NGINX

Thanks

Lots of ideas and inspiration taken from https://freek.dev/1228-introducing-laravel-websockets-an-easy-to-use-websocket-server-implemented-in-php