https://github.com/luzrain/workerman-bundle
Workerman runtime for symfony applications
https://github.com/luzrain/workerman-bundle
symfony-bundle workerman workerman-bundle
Last synced: 11 months ago
JSON representation
Workerman runtime for symfony applications
- Host: GitHub
- URL: https://github.com/luzrain/workerman-bundle
- Owner: luzrain
- License: mit
- Created: 2023-08-10T13:47:11.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2024-02-15T15:59:24.000Z (about 2 years ago)
- Last Synced: 2025-03-24T17:21:22.806Z (11 months ago)
- Topics: symfony-bundle, workerman, workerman-bundle
- Language: PHP
- Homepage:
- Size: 133 KB
- Stars: 27
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Workerman runtime for symfony applications
[](../../actions/workflows/tests.yaml)
[Workerman](https://github.com/walkor/workerman) is a high-performance, asynchronous event-driven PHP framework written in pure PHP.
This bundle provides a Workerman integration in Symfony, allowing you to easily create a http server, scheduler and supervisor all in one place.
This bundle allows you to replace a traditional web application stack like php-fpm + nginx + cron + supervisord, all written in pure PHP (no Go, no external binaries).
The request handler works in an event loop which means the Symfony kernel and the dependency injection container are preserved between requests,
making your application faster with less (or no) code changes.
## Getting started
### Install composer packages
```bash
$ composer require luzrain/workerman-bundle nyholm/psr7
```
### Enable the bundle
```php
['all' => true],
];
```
### Configure the bundle
A minimal configuration might look like this.
For all available options with documentation, see the command output.
```bash
$ bin/console config:dump-reference workerman
```
```yaml
# config/packages/workerman.yaml
workerman:
servers:
- name: 'Symfony webserver'
listen: http://0.0.0.0:80
processes: 4
reload_strategy:
exception:
active: true
file_monitor:
active: true
```
### Start application
```bash
$ APP_RUNTIME=Luzrain\\WorkermanBundle\\Runtime php public/index.php start
```
\* For better performance, Workerman recommends installing the _php-event_ extension.
## Reload strategies
Because of the asynchronous nature of the server, the workers reuse loaded resources on each request. This means that in some cases we need to restart workers.
For example, after an exception is thrown, to prevent services from being in an unrecoverable state. Or every time you change the code in the IDE.
There are a few restart strategies that are implemented and can be enabled or disabled depending on the environment.
- **exception**
Reload worker each time that an exception is thrown during the request handling.
- **max_requests**
Reload worker on every N request to prevent memory leaks.
- **file_monitor**
Reload all workers each time you change the files**.
- **always**
Reload worker after each request.
** It is highly recommended to install the _php-inotify_ extension for file monitoring. Without it, monitoring will work in polling mode, which can be very cpu and disk intensive for large projects.
See all available options for each strategy in the command output.
```bash
$ bin/console config:dump-reference workerman reload_strategy
```
### Implement your own reload strategies
You can create reload strategy with your own logic by implementing the RebootStrategyInterface and adding the `workerman.reboot_strategy` tag to the service.
```php