👀 New:

• ✏️ RR workers pool, worker, worker_watcher now has their own log levels. stderr/stdout logged as before at the info log level. All other messages moved to the debug log level except a few events from the worker_watcher when RR can't allocate the new worker which is moved to the warn.
• ✏️ Use the common logger for the whole roadrunner-sdk and roadrunner-plugins.
• ✏️ .rr.yaml now support versions. You may safely use your old configurations w/o specifying versions. Configuration w/o version will be treated as 2.6. It is safe to use configuration w/o version or with version 2.6 with RR 2.7 because RR is able to automatically transform the old configuration. But if you use configuration version 2.7 you must update the jobs pipelines config. At this point we can guarantee, that no breaking changes will be introduced in the configuration w/o auto-convert from the older configuration version For example, if we introduce a configuration update let's say in version 2.10, we will support automatic conversion from at least 2 previous versions w/o involving the user into the process. In the example case, versions 2.9 and 2.8 will be automatically converted. From our release cycle, you will have at least 3 months to update the configuration from version 2.8 and 2 months from 2.9.Version located at the top of the .rr.yaml:

Compatibility matrix located here: link

version: "2.7"

# ..... PLUGINS ......

Before:

  pipelines:
    test-local:
      driver: memory
      priority: 10
      prefetch: 10000

    test-local-1:
      driver: boltdb
      priority: 10
      file: "rr.db"
      prefetch: 10000

    test-local-2:
      driver: amqp
      prefetch: 10
      priority: 1
      queue: test-1-queue
      exchange: default
      exchange_type: direct
      routing_key: test
      exclusive: false
      multiple_ack: false
      requeue_on_fail: false

    test-local-3:
      driver: beanstalk
      priority: 11
      tube_priority: 1
      tube: default-1
      reserve_timeout: 10s

    test-local-4:
      driver: sqs
      priority: 10
      prefetch: 10
      visibility_timeout: 0
      wait_time_seconds: 0
      queue: default
      attributes:
        DelaySeconds: 0
        MaximumMessageSize: 262144
        MessageRetentionPeriod: 345600
        ReceiveMessageWaitTimeSeconds: 0
        VisibilityTimeout: 30
      tags:
        test: "tag"

    test-local-5:
      driver: nats
      priority: 2
      prefetch: 100
      subject: default
      stream: foo
      deliver_new: true
      rate_limit: 100
      delete_stream_on_stop: false
      delete_after_ack: false

After: Now, pipelines have only driver key with the configuration under the config key. We did that to uniform configuration across all drivers (like in the KV).

  pipelines:
    test-local:
      driver: memory

      config: # <------------------ NEW
        priority: 10
        prefetch: 10000

    test-local-1:
      driver: boltdb

      config: # <------------------ NEW
        priority: 10
        file: "test-local-1-bolt.db"
        prefetch: 10000

    test-local-2:
      driver: amqp

      config: # <------------------ NEW
        priority: 11
        prefetch: 100
        queue: test-12-queue
        exchange: default
        exchange_type: direct
        routing_key: test
        exclusive: false
        multiple_ack: false
        requeue_on_fail: false

    test-local-3:
      driver: beanstalk

      config: # <------------------ NEW
        priority: 11
        tube_priority: 1
        tube: default-2
        reserve_timeout: 10s

    test-local-4:
      driver: sqs

      config: # <------------------ NEW
        priority: 10
        prefetch: 10
        visibility_timeout: 0
        wait_time_seconds: 0
        queue: default

        attributes:
          DelaySeconds: 0
          MaximumMessageSize: 262144
          MessageRetentionPeriod: 345600
          ReceiveMessageWaitTimeSeconds: 0
          VisibilityTimeout: 30
        tags:
        test: "tag"

    test-local-5:
      driver: nats

      config: # <------------------ NEW
        priority: 2
        prefetch: 100
        subject: default
        stream: foo
        deliver_new: true
        rate_limit: 100
        delete_stream_on_stop: false
        delete_after_ack: false

• ✏️ [ALPHA] New cache HTTP middleware. It is still in alpha, but we started implementing the rfc-7234 to support Cache-Control and caching in general. In the first alpha you may test the max-age, Age, and Authorization support via the in-memory driver. (reporter: @alexander-schranz)

Configuration:

http:
# .....
    middleware: ["cache"]
    cache:
        driver: memory
        cache_methods: ["GET", "HEAD", "POST"] # only GET in alpha
        config: {} # empty configuration for the memory

• ✏️ Logger unification. Starting this version we bound our logs to the uber/zap log library as one of the most popular and extensible.
• ✏️ API stabilization. All v2 API interfaces moved to the https://github.com/roadrunner-server/api repository. Except for logger (structure), all plugins depend only on the interfaces and don't import each other.
• ✏️ GRPC plugin now is able to work with gzipped payloads. FR (reporter @hetao29)
• ✏️ SQS plugin now detects EC2 env and uses AWS credentials instead of the static provider. FR (reporter @paulermo)
• ✏️ Jobs plugin now acknowledges responses with incorrectly formed responses to prevent the infinity loop (with the error message in the logs). BUG (reporter @sergey-telpuk)
• ✏️ protoc updated to the version v3.19.2.

🩹 Fixes:

• 🐛 Fix: RR may have missed the message from the stderr when the PHP script failed to start immediately after RR starts.
• 🐛 Fix: 200 HTTP status code instead of 400 on readiness/health bad requests. BUG
• 🐛 Fix: new_relic plugin removes/modifies more headers than it should. BUG (reporter: @arku31)

• 🐛 Fix: incorrectly passed logger from the pool to the worker.

• 🐛 Fix: Wrong binary name for the php-gen-grpc

👀 New:

• ✏️ Add events from the supervisor to the server plugin.

🩹 Fixes:

• 🐛 Fix: worker exited immediately after obtaining the response. BUG (reporter: @samdark).

📦 Packages:

• 📦 Update RoadRunner to v2.6.2

🩹 Fixes:

• 🐛 Fix: wrong metrics type for the rr_http_requests_queue, bug (reporter: @victor-sudakov)
• 🐛 Fix: memory leak when supervised static pool used. PR.

📦 Packages:

• 📦 Update endure to v1.1.0

📦 Packages:

• 📦 Update endure to v1.1.0

🩹 Fixes:

• 🐛 Fix: NPE in the http.Reset. BUG

👀 New:

• ✏️ informer.List RPC call return all available plugins with workers instead of all available plugins. This behavior was changed because Informer has the dependency of every RR plugin, which led to the cycles. This is not an external API and is used only internally.
• ✏️ Beanstalk queue returned to the [ALPHA] stage. It's very unstable when destroying pipelines and can lead to infinite read loops when something wrong with the connection. Use with care.
• ✏️ Go version updated to v1.17.4.

🩹 Fixes:

• 🐛 Fix: add missing plugins to the container: fileserver, http_metrics.

🩹 Fixes:

• 🐛 Fix: Random NPE on RR start. BUG

👀 New:

• ✏️ Update Go version to v1.17.3

🩹 Fixes:

• 🐛 Fix: logger incorrectly escaped HTML, JSON, and other special symbols.
• 🐛 Fix: add missing configuration sections to the .rr.yaml.

👀 New:

• ✏️ New internal message bus. Available globally. Supports wildcard subscriptions (for example: http.* will subscribe you to all events coming from the http plugin). The subscriptions can be made from any RR plugin to any RR plugin.
• ✏️ Now, RR will show in the returned error the bad header content in case of CRC mismatch error. More info in the PR.
• ✏️ [BETA] Support for the New Relic observability platform. A sample of the client library might be found here. (Thanks @arku31) New Relic middleware is a part of the HTTP plugin, thus configuration should be inside it:

http:
  address: 127.0.0.1:15389
  middleware: [ "new_relic" ] <------- NEW
  new_relic: <---------- NEW
    app_name: "app"
    license_key: "key"
  pool:
    num_workers: 10
    allocate_timeout: 60s
    destroy_timeout: 60s

License key and application name could be set via environment variables: (leave app_name and license_key empty)

• license_key: NEW_RELIC_LICENSE_KEY.
• app_name: NEW_RELIC_APP_NAME.

To set the New Relic attributes, the PHP worker should send headers values withing the rr_newrelic header key. Attributes should be separated by the :, for example foo:bar, where foo is a key and bar is a value. New Relic attributes sent from the worker will not appear in the HTTP response, they will be sent directly to the New Relic.

To see the sample of the PHP library, see the @arku31 implementation: https://github.com/arku31/roadrunner-newrelic

The special key which PHP may set to overwrite the transaction name is: transaction_name. For example: transaction_name:foo means: set transaction name as foo. By default, RequestURI is used as the transaction name.

        $resp = new \Nyholm\Psr7\Response();
        $rrNewRelic = [
            'shopId:1', //custom data
            'auth:password', //custom data
            'transaction_name:test_transaction' //name - special key to override the name. By default it will use requestUri.
        ];

        $resp = $resp->withHeader('rr_newrelic', $rrNewRelic);

• ✏️ [BETA] New plugin: TCP. The TCP plugin is used to handle raw TCP payload with a bi-directional protocol between the RR server and PHP worker.

PHP client library: https://github.com/spiral/roadrunner-tcp

Configuration:

rpc:
  listen: tcp://127.0.0.1:6001

server:
  command: "php ../../psr-worker-tcp-cont.php"

tcp:
  servers:
    server1:
      addr: 127.0.0.1:7778
      delimiter: "\r\n"
    server2:
      addr: 127.0.0.1:8811
      read_buf_size: 10
    server3:
      addr: 127.0.0.1:8812
      delimiter: "\r\n"
      read_buf_size: 1

  pool:
    num_workers: 5
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ New HTTP middleware: http_metrics.

Config:

http:
  address: 127.0.0.1:15389
  middleware: [ "http_metrics" ] <------- NEW
  pool:
    num_workers: 10
    allocate_timeout: 60s
    destroy_timeout: 60s

All old and new http metrics will be available after the middleware is activated. Be careful, this middleware may slow down your requests. New metrics:

- `rr_http_requests_queue_sum` - number of queued requests.
- `rr_http_no_free_workers_total` - number of the occurrences of the `NoFreeWorkers` errors.

• ✏️ New file server to serve static files. It works on a different address, so it doesn't affect the HTTP performance. It uses advanced configuration specific for the static file servers. It can handle any number of directories with its own HTTP prefixes. Config:

fileserver:
  # File server address
  #
  # Error on empty
  address: 127.0.0.1:10101
  # Etag calculation. Request body CRC32.
  #
  # Default: false
  calculate_etag: true

  # Weak etag calculation
  #
  # Default: false
  weak: false

  # Enable body streaming for files more than 4KB
  #
  # Default: false
  stream_request_body: true

  serve:
    # HTTP prefix
    #
    # Error on empty
  - prefix: "/foo"

    # Directory to serve
    #
    # Default: "."
    root: "../../../tests"

    # When set to true, the server tries minimizing CPU usage by caching compressed files
    #
    # Default: false
    compress: false

    # Expiration duration for inactive file handlers. Units: seconds.
    #
    # Default: 10, use a negative value to disable it.
    cache_duration: 10

    # The value for the Cache-Control HTTP-header. Units: seconds
    #
    # Default: 10 seconds
    max_age: 10

    # Enable range requests
    # https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests
    #
    # Default: false
    bytes_range: true

  - prefix: "/foo/bar"
    root: "../../../tests"
    compress: false
    cache_duration: 10s
    max_age: 10
    bytes_range: true

• ✏️ on_init option for the server plugin. on_init code executed before the regular command and can be used to warm up the application for example. Failed on_init command doesn't affect the main command, so, the RR will continue to run. Thanks (@OO00O0O)

Config:

# Application server settings (docs: https://roadrunner.dev/docs/php-worker)
server:
  on_init: <----------- NEW
    # Command to execute before the main server's command
    #
    # This option is required if using on_init
    command: "any php or script here"

    # Script execute timeout
    #
    # Default: 60s [60m, 60h], if used w/o units its means - NANOSECONDS.
    exec_timeout: 20s

    # Environment variables for the worker processes.
    #
    # Default: <empty map>
    env:
      - SOME_KEY: "SOME_VALUE"
      - SOME_KEY2: "SOME_VALUE2"

  # ..REGULAR SERVER OPTIONS...

• ✏️ [BETA] GRPC can handle multiply proto files. Config:

# GRPC service configuration
grpc:
    # Proto files to use
    #
    # This option is required. At least one proto file must be specified.
    proto:
        - "first.proto"
        - "second.proto"

## ... OTHER REGULAR GRPC OPTIONS ...

• ✏️ New allow configuration option for the http.uploads and multipart requests. The new option allows you to filter upload extensions knowing only allowed. Now, there is no need to have a looong list with all possible extensions to forbid. FR (Thanks @rjd22) http.uploads.forbid has a higher priority, so, if you have duplicates in the http.uploads.allow and http.uploads.forbid the duplicated extension will be forbidden. Config:

http:
  address: 127.0.0.1:18903
  max_request_size: 1024
  middleware: ["pluginMiddleware", "pluginMiddleware2"]
  uploads:
    forbid: [".php", ".exe", ".bat"]
    allow: [".html", ".aaa" ] <------------- NEW
  trusted_subnets:
    [
      "10.0.0.0/8",
      "127.0.0.0/8",
      "172.16.0.0/12",
      "192.168.0.0/16",
      "::1/128",
      "fc00::/7",
      "fe80::/10",
    ]
  pool:
    num_workers: 2
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ Beanstalk queue reject stop RPC calls if there are jobs in the priority queue associated with the requested pipeline.

• ✏️ Startup message when the RR has started.

🩹 Fixes:

• 🐛 Fix: GRPC server will show message when started.
• 🐛 Fix: Static plugin headers were added to all requests. BUG
• 🐛 Fix: zombie processes in the pool.debug mode.

📦 Packages:

• 📦 roadrunner v2.6.0
• 📦 roadrunner-plugins v2.6.0
• 📦 roadrunner-temporal v1.0.11
• 📦 endure v1.0.8
• 📦 goridge v3.2.4
• 📦 temporal.io/sdk v1.11.1

Full Changelog: https://github.com/spiral/roadrunner-binary/compare/v2.5.6...v2.5.7

Full Changelog: https://github.com/spiral/roadrunner-binary/compare/v2.5.5...v2.5.6

Full Changelog: https://github.com/spiral/roadrunner-binary/compare/v2.5.4...v2.5.5

🩹 Fixes:

• 🐛 Fix: worker's channel deadlock when using TTL. Thanks @dstrop

🩹 Fixes:

• 🐛 Fix: panic in the TLS layer. The http plugin used http server instead of https in the rootCA routine.

👀 New:

• ✏️ [BETA] Support for the New Relic observability platform. Sample of the client library might be found here. (Thanks @arku31)
  New Relic middleware is a part of the HTTP plugin, thus configuration should be inside it:

http:
  address: 127.0.0.1:15389
  middleware: [ "new_relic" ]
  new_relic:
    app_name: "app"
    license_key: "key"
  pool:
    num_workers: 10
    allocate_timeout: 60s
    destroy_timeout: 60s

License key and application name could be set via environment variables: (leave app_name and license_key empty)

• license_key: NEW_RELIC_LICENSE_KEY.
• app_name: NEW_RELIC_APP_NAME.

To set the New Relic attributes, the PHP worker should send headers values witing the rr_newrelic header key. Attributes should be separated by the :, for example foo:bar, where foo is a key and bar is a value. New Relic attributes sent from the worker will not appear in the HTTP response, they will be sent directly to the New Relic.

The special key which PHP may set to overwrite the transaction name is: transaction_name. For example: transaction_name:foo means: set transaction name as foo. By default, RequestURI is used as the transaction name.

        $resp = new \Nyholm\Psr7\Response();
        $rrNewRelic = [
            'shopId:1', //custom data
            'auth:password', //custom data
            'transaction_name:test_transaction' //name - special key to override the name. By default it will use requestUri.
        ];

        $resp = $resp->withHeader('rr_newrelic', $rrNewRelic);

🩹 Fixes:

• 🐛 Fix: ASLR builds causes problems in the docker.

🩹 Fixes:

• 🐛 Fix: base64 response instead of json in some edge cases.

💔 Breaking change:

• 🔨 Some drivers now use a new config key to handle local configuration. Involved plugins and drivers:
• plugins: broadcast, kv
• drivers: memory, redis, memcached, boltdb.

Old style:

broadcast:
    default:
        driver: memory
        interval: 1

New style:

broadcast:
  default:
    driver: memory
     config: {} <--------------- NEW

kv:
  memory-rr:
    driver: memory
    config: <--------------- NEW
      interval: 1

kv:
  memcached-rr:
    driver: memcached
    config: <--------------- NEW
       addr:
         - "127.0.0.1:11211"

broadcast:
  default:
    driver: redis
    config: <------------------ NEW
      addrs:
        - "127.0.0.1:6379"

👀 New:

• ✏️ [BETA] GRPC plugin update to v2.
• ✏️ Roadrunner-plugins repository. This is the new home for the roadrunner plugins with documentation, configuration samples, and common problems.
• ✏️ [BETA] Let's Encrypt support. RR now can obtain an SSL certificate/PK for your domain automatically. Here is the new configuration:

    ssl:
      # Host and port to listen on (eg.: `127.0.0.1:443`).
      #
      # Default: ":443"
      address: "127.0.0.1:443"

      # Use ACME certificates provider (Let's encrypt)
      acme:
        # Directory to use as a certificate/pk, account info storage
        #
        # Optional. Default: rr_cache
        certs_dir: rr_le_certs

        # User email
        #
        # Used to create LE account. Mandatory. Error on empty.
        email: you-email-here@email

        # Alternate port for the http challenge. Challenge traffic should be redirected to this port if overridden.
        #
        # Optional. Default: 80
        alt_http_port: 80,


        # Alternate port for the tls-alpn-01 challenge. Challenge traffic should be redirected to this port if overridden.
        #
        # Optional. Default: 443.
        alt_tlsalpn_port: 443,

        # Challenge types
        #
        # Optional. Default: http-01. Possible values: http-01, tlsalpn-01
        challenge_type: http-01

        # Use production or staging endpoints. NOTE, try to use the staging endpoint (`use_production_endpoint`: `false`) to make sure, that everything works correctly.
        #
        # Optional, but for production should be set to true. Default: false
        use_production_endpoint: true

        # List of your domains to obtain certificates
        #
        # Mandatory. Error on empty.
        domains: [
            "your-cool-domain.here",
            "your-second-domain.here"
        ]

• ✏️ Add a new option to the logs plugin to configure the line ending. By default, used \n.

New option:

# Logs plugin settings
logs:
    (....)
    # Line ending
    #
    # Default: "\n".
    line_ending: "\n"

• ✏️ HTTP Access log support at the Info log level.

http:
  address: 127.0.0.1:55555
  max_request_size: 1024
  access_logs: true <-------- Access Logs ON/OFF
  middleware: []

  pool:
    num_workers: 2
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ HTTP middleware to handle X-Sendfile header. Middleware reads the file in 10MB chunks. So, for example for the 5Gb file, only 10MB of RSS will be used. If the file size is smaller than 10MB, the middleware fits the buffer to the file size.

http:
  address: 127.0.0.1:44444
  max_request_size: 1024
  middleware: ["sendfile"] <----- NEW MIDDLEWARE

  pool:
    num_workers: 2
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ Service plugin now supports env variables passing to the script/executable/binary/any like in the server plugin:

service:
  some_service_1:
    command: "php test_files/loop_env.php"
    process_num: 1
    exec_timeout: 5s # s,m,h (seconds, minutes, hours)
    remain_after_exit: true
    env:  <----------------- NEW
      foo: "BAR"
    restart_sec: 1

• ✏️ Server plugin can accept scripts (sh, bash, etc) in it's command configuration key:

server:
    command: "./script.sh OR sh script.sh" <--- UPDATED
    relay: "pipes"
    relay_timeout: "20s"

The script should start a worker as the last command. For the pipes, scripts should not contain programs, which can close stdin, stdout or stderr.

• ✏️ Nats jobs driver support - PR.

nats:
  addr: "demo.nats.io"

jobs:
  num_pollers: 10
  pipeline_size: 100000
  pool:
    num_workers: 10
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

  pipelines:
    test-1:
      driver: nats
      prefetch: 100
      subject: "default"
      stream: "foo"
      deliver_new: "true"
      rate_limit: 100
      delete_stream_on_stop: false
      delete_after_ack: false
      priority: 2

  consume: [ "test-1" ]

• Driver uses NATS JetStream API and is not compatible with non-js API.

• ✏️ Response API for the NATS, RabbitMQ, SQS and Beanstalk drivers. This means, that you'll be able to respond to a specified in the response queue. Limitations:

  • To send a response to the queue maintained by the RR, you should send it as a Job type. There are no limitations for the responses into the other queues (tubes, subjects).
  • Driver uses the same endpoint (address) to send the response as specified in the configuration.

🩹 Fixes:

• 🐛 Fix: local and global configuration parsing.
• 🐛 Fix: boltdb-jobs connection left open after RPC close command.
• 🐛 Fix: close beanstalk connection and release associated resources after pipeline stopped.
• 🐛 Fix: grpc plugin fails to handle requests after calling reset.
• 🐛 Fix: superfluous response.WriteHeader call when connection is broken.

📦 Packages:

• 📦 roadrunner v2.5.0
• 📦 roadrunner-plugins v2.5.0
• 📦 roadrunner-temporal v1.0.10
• 📦 endure v1.0.6
• 📦 goridge v3.2.3

What's Changed

• feat(update): rc.2 pre-release by @rustatian in https://github.com/spiral/roadrunner-binary/pull/113

Full Changelog: https://github.com/spiral/roadrunner-binary/compare/v2.5.0-rc.1...v2.5.0-rc.2

• ✏️ Nats jobs driver support - PR.

nats:
  addr: "demo.nats.io"

jobs:
  num_pollers: 10
  pipeline_size: 100000
  pool:
    num_workers: 10
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

  pipelines:
    test-1:
      driver: nats
      prefetch: 100
      subject: "default"
      stream: "foo"
      deliver_new: "true"
      rate_limit: 100
      delete_stream_on_stop: false
      delete_after_ack: false
      priority: 2

  consume: [ "test-1" ]

• Driver uses NATS JetStream API and is not compatible with non-js API.

• ✏️ Response API for the NATS, RabbitMQ, SQS and Beanstalk drivers. This means, that you'll be able to respond to a specified in the response queue. Limitations:

  • To send a response to the queue maintained by the RR, you should send it as a Job type. There is no limitation for the other queues (tubes, subjects) responses.
  • Driver uses the same endpoint (address) to send the response as specified in the configuration.

• ✏️ Add a new option to the log plugin to configure the line ending. By default, used \n.

New option:

# Logs plugin settings
logs:
    (....)
    # Line ending
    #
    # Default: "\n".
    line_ending: "\n"

• ✏️ Access log support at the Info log level.

http:
  address: 127.0.0.1:55555
  max_request_size: 1024
  access_logs: true <-------- Access Logs ON/OFF
  middleware: []

  pool:
    num_workers: 2
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ HTTP middleware to handle X-Sendfile header.

http:
  address: 127.0.0.1:44444
  max_request_size: 1024
  middleware: ["sendfile"] <----- NEW MIDDLEWARE

  pool:
    num_workers: 2
    max_jobs: 0
    allocate_timeout: 60s
    destroy_timeout: 60s

• ✏️ Service plugin now supports env variables passing to the script/executable/binary/any:

service:
  some_service_1:
    command: "php test_files/loop_env.php"
    process_num: 1
    exec_timeout: 5s # s,m,h (seconds, minutes, hours)
    remain_after_exit: true
    env:  <----------------- NEW
      foo: "BAR"
    restart_sec: 1

• ✏️ Server plugin can accept scripts (sh, bash, etc) in it's command configuration key:

server:
    command: "./script.sh OR sh script.sh" <--- UPDATED
    relay: "pipes"
    relay_timeout: "20s"

The script should start a worker as the last command. For the pipes, scripts should not contain programs, which can close stdin, stdout or stderr.

🩹 Fixes:

• 🐛 Fix: grpc plugin fails to handle requests after calling reset.

💔 BC:

• 🔨 Some drivers now use a new config key to handle local configuration. Involved plugins and drivers:
• plugins: broadcast, kv
• drivers: memory, redis, memcached, boltdb.

ATTENTION!!!, this is the configuration BC release, please, update your configuration:

Old style:

broadcast:
  default:
    driver: memory
    interval: 1

New style:

broadcast:
  default:
    driver: memory
    config: {} <--------------- NEW

kv:
  memory-rr:
    driver: memory
    config: <--------------- NEW
      interval: 1

kv:
  memcached-rr:
    driver: memcached
    config: <--------------- NEW
      addr:
        - "127.0.0.1:11211"

broadcast:
  default:
    driver: redis
    config: <------------------ NEW
      addrs:
        - "127.0.0.1:6379"

👀 New:

• ✏️ [BETA] GRPC plugin updated to v2.
• ✏️ Roadrunner-plugins repository. This is the new home for the roadrunner plugins with documentation, configuration samples, and common problems.
• ✏️ [BETA] Let's Encrypt support. RR now can obtain an SSL certificate/PK for your domain automatically. Here is the new configuration:

    ssl:
      # Host and port to listen on (eg.: `127.0.0.1:443`).
      #
      # Default: ":443"
      address: "127.0.0.1:443"

      # Use ACME certificates provider (Let's encrypt)
      acme:
        # Directory to use as a certificate/pk, account info storage
        #
        # Optional. Default: rr_cache
        certs_dir: rr_le_certs

        # User email
        #
        # Used to create LE account. Mandatory. Error on empty.
        email: you-email-here@email

        # Alternate port for the http challenge. Challenge traffic should be redirected to this port if overridden.
        #
        # Optional. Default: 80
        alt_http_port: 80,


        # Alternate port for the tls-alpn-01 challenge. Challenge traffic should be redirected to this port if overridden.
        #
        # Optional. Default: 443.
        alt_tlsalpn_port: 443,

        # Challenge types
        #
        # Optional. Default: http-01. Possible values: http-01, tlsalpn-01
        challenge_type: http-01

        # Use production or staging endpoints. NOTE, try to use the staging endpoint (`use_production_endpoint`: `false`) to make sure, that everything works correctly.
        #
        # Optional, but for production should be set to true. Default: false
        use_production_endpoint: true

        # List of your domains to obtain certificates
        #
        # Mandatory. Error on empty.
        domains: [
            "your-cool-domain.here",
            "your-second-domain.here"
        ]

• ✏️ Add a new options to the service plugin. Service plugin will not use std RR logger as output in the flavor of raw output.

New options:

# Service plugin settings
service:
  some_service_1:
    (....)
    # Console output
    #
    # Default: stderr. Available options: stderr, stdout
    output: "stderr"

    # Endings for the stderr/stdout output
    #
    # Default: "\n". Available options: any.
    line_ending: "\n"

    # Color for regular output
    #
    # Default: none. Available options: white, red, green, yellow, blue, magenta
    color: "green"

    # Color for the process errors
    #
    # Default: none. Available options: white, red, green, yellow, blue, magenta
    err_color: "red"

!!! Be careful, now, there is no logger plugin dependency for the service plugin. That means, that if you used json output, now, you need to serialize data on the executable (in the command) side.

🩹 Fixes:

• 🐛 Fix: local and global configuration parsing.
• 🐛 Fix: bug with the boltdb-jobs connection left open after RPC close command.
• 🐛 Fix: close beanstalk connection and release associated resources after pipeline stopped.

📦 Packages:

• 📦 roadrunner v2.5.0
• 📦 roadrunner-plugins v2.5.0
• 📦 roadrunner-temporal v1.0.10
• 📦 goridge v3.2.2

💔 BC:

• 🔨 Some drivers now use a new config key to handle local configuration. Involved plugins and drivers:
• plugins: broadcast, kv
• drivers: memory, redis, memcached, boltdb.

ATTENTION!!!, this is the configuration BC release, please, update your configuration:

Old style:

broadcast:
    default:
        driver: memory
        interval: 1

New style:

broadcast:
    default:
        driver: memory
        config: {} <--------------- NEW

kv:
    memory-rr:
        driver: memory
        config: <--------------- NEW
            interval: 1

kv:
    memcached-rr:
        driver: memcached
        config: <--------------- NEW
            addr:
                - "127.0.0.1:11211"

broadcast:
  default:
    driver: redis
    config: <------------------ NEW
      addrs:
        - "127.0.0.1:6379"

👀 New:

• ✏️ [BETA] GRPC plugin updated to v2.
• ✏️ Roadrunner-plugins repository. This is the new home for the roadrunner plugins with documentation, configuration samples, and common problems. Feel free to read new docs for the plugins: docs

🩹 Fixes:

• 🐛 Fix: local and global configuration parsing

📦 Packages:

• 📦 Roadrunner v2.5.0
• 📦 Roadrunner-plugins v2.5.0
• 📦 Roadrunner-temporal v1.0.10

🩹 Fixes:

• 🐛 Fix: bug with the not-idempotent call to the attributes.Init.
• 🐛 Fix: memory jobs driver behavior. Now memory driver starts consuming automatically if the user consumes the pipeline in the configuration.

📦 Packages:

• 📦 Update RR to v2.4.1

🩹 Fixes:

• 🐛 Fix: absent column in the workers -i output.