bangpound/invoker-bundle

Manage server processes in your Symfony development environment

Invoker Bundle

This bundle imitates some of the functionality of invoker to run services in development environments., _(*1)

Usage

Enable the bundle in your kernel., _(*2)

``` php <?php // app/AppKernel.php, <sub>(*3)</sub>

public function registerBundles() { $bundles = array( // ... new Bangpound\Bundle\InvokerBundle\BangpoundInvokerBundle(), ); }, <sub>(*4)</sub>

Create ProcessBuilder services for each process this bundle should launch.

```yaml
    bangpound_castle.process.elasticsearch:
        class: Bangpound\Bundle\InvokerBundle\Process\ProcessBuilder
        arguments: [ ["/usr/local/bin/elasticsearch", "--config=/usr/local/opt/elasticsearch/config/elasticsearch.yml"] ]
        calls:
            - [ setTimeout, [ ~ ]]
        tags:
            - { name: bangpound_invoker.server }

    bangpound_castle.process.couchdb:
        class: Bangpound\Bundle\InvokerBundle\Process\ProcessBuilder
        arguments: [ ["couchdb" ] ]
        calls:
            - [ setTimeout, [ ~ ]]
        tags:
            - { name: bangpound_invoker.server }

    bangpound_castle.process.rabbitmq:
        class: Bangpound\Bundle\InvokerBundle\Process\ProcessBuilder
        arguments: [ ["rabbitmq-server"] ]
        calls:
            - [ setTimeout, [ ~ ]]
        tags:
            - { name: bangpound_invoker.server }

Then run the Symfony console command invoker., <sub>(*5)</sub>

./bin/console invoker -vv

Using the verbosity flags will cause process output to be logged to the console, which is usually desireable., <sub>(*6)</sub>

This is a bundle that should only be used for development environments. Do not use this bundle in production. Instead use your operating system's service initialization such as systemd or init.d and/or use supervisord., <sub>(*7)</sub>