Download the PHP package tailrdigital/sulu-messenger-failed-queue-bundle without Composer
On this page you can find all versions of the php package tailrdigital/sulu-messenger-failed-queue-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package sulu-messenger-failed-queue-bundle
Sulu Messenger Failed Queue
This package provides a Sulu admin panel for managing the failed messages in the failure queue of symfony/messenger.
Via the admin panel you are able to check the error/exception details of each failed message, and you can trigger a requeue/retry if needed.
Demo
Installation
Register the bundle
Make sure the bundle is activated in config/bundles.php:
Register new admin routes
You need to manually register the failed queue admin controller routes in the file config/routes_admin.yaml.
Add node dependency
Register an additional module in your admin's node dependencies via assets/admin/package.json:
Make sure to load the additional node module in your admin's assets/admin/index.js or assets/admin/app.js file:
Recompile your admin assets
Setting up your failure queue
You can set up the symfony/messenger queue according to this example configuration inside config/packages/messenger.yaml
Permissions
Make sure you've set the correct permissions in the Sulu admin for this package. Go to Settings > User Roles and enable the permissions you need. Afterwards you could find the Failed Queue view/panel via Settings > Failed Queue.
Configuration
If you have a non-default failure queue configuration, you are able to overwrite our default settings by creating a config/packages/sulu_messenger_failed_queue.yaml file.
If needed you can define the configured (failed) transport service definition or alias name via failure_transport_service.
On the other hand you could modify the database table name via failure_transport_table and define the (failed) queue name via failure_transport_queue_name.
Known limitations
The symfony/messenger package has support for multiple failure queues/transports, but this package only has support for visualizing and managing one (doctrine) failure queue/transport.
All versions of sulu-messenger-failed-queue-bundle with dependencies
azjezz/psl Version ^2.6 || ^3.0
doctrine/dbal Version ^3.0
doctrine/orm Version ^2.14
sulu/sulu Version ^2.5
jackalope/jackalope-doctrine-dbal Version ^1.6 || ^2.0
symfony/config Version ^6.0
symfony/console Version ^6.0
symfony/dependency-injection Version ^6.0
symfony/http-foundation Version ^6.0
symfony/doctrine-messenger Version ^6.0
symfony/messenger Version ^6.0