Download the PHP package jean-beru/pipeline-bundle without Composer
On this page you can find all versions of the php package jean-beru/pipeline-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 pipeline-bundle
PipelineBundle
Pipeline bundle for Symfony.
Install
Install bundle : ``
If you do not use symfony/flex, you have to add this bundle to your
config/bundles.php file :
Configuration
pipelines defines all pipelines. The key defines pipeline's name.
pipelines.__NAME__.stages defines services to use as stages in this pipeline.
pipelines.__NAME__.processor (optional) defines a specific processor to use with this pipeline. See "What is a
processor ?" section below.
Example :
Inject pipeline services
Using service ID
All defined pipeline is added as a service named jeanberu_pipeline.pipeline.__NAME__.
With the previous configuration, we will be able to inject 3 pipelines :
- jeanberu_pipeline.pipeline.update_stock
- jeanberu_pipeline.pipeline.export
- jeanberu_pipeline.pipeline.some_computations
Using autowiring
All defined pipeline can be autowired using its name PipelineInterface $__NAME__Pipeline.
With the previous configuration, we will be able to inject 3 pipelines :
- Pipeline $updateStockPipeline
- Pipeline $exportPipeline
- Pipeline $someComputationsPipeline
Usage
Each service implements the League\Pipeline\PipelineInterface interface.
In this example, some_computations pipeline defined before will make some operations on the payload and will return
it.
What are pipeline and stage ?
A stage represents a task to execute with a payload. It must be a callable. You can implement
League\Pipeline\StageInterface to ensure that your stage can be called.
A pipeline represents chained stages. You can see it like a CLI command: stage_1 | stage_2 | stage_3. Each stage
receives the previously returned payload.
Since pipelines implements League\Pipeline\PipelineInterface which implements itself League\Pipeline\StageInterface,
you can use it as a stage to make re-usable pipelines (a.k.a. pipeline-ception). Ex: stage_1 | pipeline_1 | stage_3.
What is a processor ?
To execute a pipeline, a processor is used. It must implement League\Pipeline\ProcessorInterface. You can use your
own service if you want to.
If symfony/event-dispatcher is available, a jeanberu_pipeline.processor.event_dispatcher_processor processor
will be available (see EventDispatcherProcessor) to dispatch some
events :
- JeanBeru\PipelineBundle\Event\BeforeProcessorEvent
- JeanBeru\PipelineBundle\Event\BeforeStageEvent
- JeanBeru\PipelineBundle\Event\AfterStageEvent
- JeanBeru\PipelineBundle\Event\AfterProcessorEvent
Test
Install dependencies :
Run tests :
All versions of pipeline-bundle with dependencies
league/pipeline Version ^1.0
symfony/config Version ^5.0|^6.0|^7.0
symfony/dependency-injection Version ^5.0|^6.0|^7.0
symfony/http-kernel Version ^5.0|^6.0|^7.0