Download the PHP package keboola/messenger-bundle without Composer
On this page you can find all versions of the php package keboola/messenger-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
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.
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 PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- 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.
Please rate this library. Is it a good library?
Informations about the package messenger-bundle
Keboola Messenger Bundle
Symfony Messenger bundle preconfigured for Keboola platform.
Installation
Install the package with Composer:
Configuration
Bundle supports following configuration options:
- platform - optional,
aws,azure,gcpornull- when not set (or set to
null) the bundle will not set up any transport
- when not set (or set to
- connection_events_queue_dsn - optional, DSN for connection events queue
- connection_audit_log_queue_dsn - optional, DSN for connection audit log queue
See documentation of each platform driver for details on DSN syntax
- for AWS use the queue URL, ex.
https://sqs.eu-central-1.amazonaws.com/025303414634/queue-name, see https://symfony.com/doc/current/messenger.html#amazon-sqs for details - for Azure use format
azure://<sas-key-name>:<sas-kev-value>@<servicebus-namespace>?entity_path=<servicebus-queue-name>, see https://github.com/AymDev/MessengerAzureBundle for details - for GCP use format
gps://default/<topic-name>, see https://github.com/petitpress/gps-messenger-bundle for details
Reference:
Development
Prerequisites:
awsCLI with configuredKeboola-Dev-Platform-Services-AWSAdministratorAccessprofileazCLI with configured for Keboola DEV Platform Services Team subscription- run
az account set --subscription c5182964-8dca-42c8-a77a-fa2a3c6946ea
- run
- installed
terraform(https://www.terraform.io) andjq(https://stedolan.github.io/jq) to setup local env - installed
dockerto run & develop the app
TL;DR:
Reverse-engineering events
If a problem is found in existing serializer or a new serializer needs to be implemented to support new platform, it is possible to connect to a real queue on testing environment to introspect the events structure.
The procedure is slightly different for each platform, but the general idea is the same:
- Open the testing account/project/env in web console (https://portal.azure.com, https://console.cloud.google.com etc.)
- Configure queue for the kind of event you want to debug
- on GCP create a new subscription to existing topic
- in Pub/Sub open topic you want to subscribe to
- in detail, go to Subscriptions tab and click "Create subscription"
- on AWS create a new SQS queue and subscribe it to existing SNS topic
- go to SQS and create a new queue
- go to queues list, select the queue and in "Actions" menu select "Subscribe to SNS topic"
- on Azure create a new Service Bus and subscribe it to existing Event Grid topic
- on GCP create a new subscription to existing topic
- Manually update
.env.localconfiguration to connect to the queue- set queue DSN to the queue created in previous step
- on GCP you can use your local application default credentials
- copy contents of
~/.config/gcloud/application_default_credentials.jsonto./var/gcp/private-key.json - set extra ENV
GCLOUD_PROJECT
- copy contents of
- Run
php tests/console messenger:consume <transport_name> -vvv --limit 1to receive one event from the queue
If the event is successfully consumed, you can see its contents on the output.
When you are done, don't forget to clean up after yourself and delete the queue.
License
MIT licensed, see LICENSE file.
All versions of messenger-bundle with dependencies
PHP Build Version
Package Version
Requires
php Version
>=8.2
ext-pcntl Version *
aymdev/messenger-azure-bundle Version dev-dsnParser
petitpress/gps-messenger-bundle Version ^1.6
symfony/amazon-sqs-messenger Version ^6.3
symfony/dependency-injection Version ^6.0
symfony/messenger Version ^6.0
ext-pcntl Version *
aymdev/messenger-azure-bundle Version dev-dsnParser
petitpress/gps-messenger-bundle Version ^1.6
symfony/amazon-sqs-messenger Version ^6.3
symfony/dependency-injection Version ^6.0
symfony/messenger Version ^6.0
The package keboola/messenger-bundle contains the following files
Loading the files please wait ....