Download the PHP package wisembly/amqp-bundle without Composer

On this page you can find all versions of the php package wisembly/amqp-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:
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.
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 amqp-bundle

Amqp Swarrot Bundle

This bundle integrates Swarrot into Symfony, with another approach from the SwarrotBundle. Currently in early stages of development... and opensourcing.

But, unlike the SwarrotBundle, this bundle does not allow you (...yet ?) to configure multiple consumers, and force you to use the CommandProcessor approach (Every message should be treated in the CommandProcessor, which will be treated through a Symfony Process).

Installation

The recommended way is to go through Composer. Once you have installed it, you should run the require command: composer require wisembly\amqp-bundle, and pick the latest version available on packagist (you should avoid @stable meta-constraint). Note that a flex recipe is available. :}

Configuration Reference

The configuration reference can be found through the command app/console config:dump-reference WisemblyAmqpBundle :

Usage

Concept of "Gates"

This concept is the whole difference with the Swarrot Bundle : Gates. It is a simple value object containing information on the queue / exchange to use for your actions (which connection to use, which queue it should target, which exchange should be used, which routing key, ... and configuration for these, such as should the exchange / queue be declared if not existent, and so on).

Refer to the configuration reference for more information on what is possible to configure for a "gate". Once you have at least one, you can consume from one, or publish to one. For that, see below.

Publishing a Message

You may publish a new message to a gate (access point). For that, you should retrieve the services Wisembly\AmqpBundle\GatesBag to fetch the right gate, and then use the Wisembly\AmqpBundle\Publisher service to publish a message that can be understood by the CommandProcessor :

Your message is then ready to be consumed by the consumer. But, if you don't want to use the AmqpBundle's consumer, you're not forced to use the same syntax and use whatever you need !

Consuming a Message

In order to consume the messages that are expected by this bundle, all you have to do is run the following command :

A bunch of options are available (such as activating a RPC mechanism, defining a polling interval, ...), but you can check all of those in the --help option.

Whenever a message is consumed by this consumer, it will launch a new Process to treat it, and will pass the environment and verbosity to the command that is run. The output will then be retrieved and printed on the consumer's output.

Implementing a Broker

Two brokers are built-in :

The recommended broker is to use if available the Wisembly\AmqpBundle\Broker\PeclBroker broker.

But you can implement more of those (such as a Redis one or whatever else !) by implementing the Wisembly\AmqpBundle\BrokerInterface interface. If using the autoconfigure setting of the dic 3.4+, that's all you have to do. If you want to add an alias or if not using the autoconfigure feature, you can add a wisembly.amqp.broker tag, which can have an alias (it will take the service's name if no alias are specified).

Credits

Developed with love at the Wisembly Factory, based on the SwarrotBundle.


All versions of amqp-bundle with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1
psr/log Version ^1.0
swarrot/swarrot Version ^2.0 || ^3.0
symfony/config Version ^3.0 || ^4.0
symfony/console Version ^3.0 || ^4.0
symfony/process Version ^3.4 || ^4.0
symfony/http-kernel Version ^3.0 || ^4.0
symfony/event-dispatcher Version ^3.0 || ^4.0
symfony/options-resolver Version ^3.3 || ^4.0
symfony/dependency-injection Version ^3.3 || ^4.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wisembly/amqp-bundle contains the following files

Loading the files please wait ....