Skip to content

Releases: brefphp/symfony-bridge

1.0.3

27 Aug 12:57
5b1f650
Compare
Choose a tag to compare

What's Changed

  • Allow deployments in sub directory by @Nyholm in #69

Full Changelog: 1.0.2...1.0.3

1.0.2

27 Aug 12:56
cce0757
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.0.1...1.0.2

1.0.1

20 Feb 14:09
1bab91b
Compare
Choose a tag to compare

What's Changed

  • Align BrefKernel::handle method signature with the Symfony\Component\HttpKernel\HttpKernelInterface by @smoench in #68

New Contributors

Full Changelog: 1.0.0...1.0.1

1.0.0

30 Nov 14:51
0b2ecdb
Compare
Choose a tag to compare

What's Changed

  • Symfony 7.0 support by @1ed in #67

New Contributors

  • @1ed made their first contribution in #67

Full Changelog: 0.2.2...1.0.0

0.2.2

05 Jul 08:52
f3a15f8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.2.1...0.2.2

0.2.1

15 Dec 13:26
a2e67cf
Compare
Choose a tag to compare

What's Changed

Full Changelog: 0.2.0...0.2.1

0.2.0

09 Feb 10:21
4485405
Compare
Choose a tag to compare

BC breaks over v0.1

  • Requires Symfony 5.2 or greater

Improvements

Symfony 6 compatibility by @amacrobert in #47 and @mnapoli in #50

The package now provides a Symfony Runtime (by @mnapoli in #45) that lets users:

  • Handle requests with the Kernel directly, without PHP-FPM

Extract of the documentation:

# serverless.yml

functions:
    app:
-        handler: public/index.php
+        handler: App\Kernel
        layers:
            # Switch from PHP-FPM to the "function" runtime:
-            - ${bref:layer.php-80-fpm}
+            - ${bref:layer.php-80}
        environment:
            # The Symfony process will restart every 100 requests
            BREF_LOOP_MAX: 100

The App\Kernel will be retrieved via Symfony Runtime from public/index.php.

  • Handle events with Symfony services

Extract of the documentation:

To handle other events (e.g. SQS messages with Symfony Messenger) via a class name:

# serverless.yml

functions:
    sqsHandler:
-        handler: bin/consumer.php
+        handler: App\Service\MyService
        layers:
            - ${bref:layer.php-80}

The service will be retrieved via Symfony Runtime from the Symfony Kernel returned by public/index.php.

Note: the service must be configured as public (public: true) in the Symfony configuration.

Full Changelog: 0.1.3...0.2.0

0.2.0-beta1

30 Dec 15:19
Compare
Choose a tag to compare

First beta release for v0.2.0.

BC breaks

  • Requires Symfony 5.2 or greater

Improvements

Symfony 6 compatibility by @amacrobert in #47 and @mnapoli in #50

The package now provides a Symfony Runtime (by @mnapoli in #45) that lets users:

  • Handle requests with the Kernel directly, without PHP-FPM

Extract of the documentation:

# serverless.yml

functions:
    app:
-        handler: public/index.php
+        handler: App\Kernel
        layers:
            # Switch from PHP-FPM to the "function" runtime:
-            - ${bref:layer.php-80-fpm}
+            - ${bref:layer.php-80}
        environment:
            # The Symfony process will restart every 100 requests
            BREF_LOOP_MAX: 100

The App\Kernel will be retrieved via Symfony Runtime from public/index.php.

  • Handle events with Symfony services

Extract of the documentation:

To handle other events (e.g. SQS messages with Symfony Messenger) via a class name:

# serverless.yml

functions:
    sqsHandler:
-        handler: bin/consumer.php
+        handler: App\Service\MyService
        layers:
            - ${bref:layer.php-80}

The service will be retrieved via Symfony Runtime from the Symfony Kernel returned by public/index.php.

Note: the service must be configured as public (public: true) in the Symfony configuration.

New Contributors

Full Changelog: 0.1.3...0.2.0-beta1

0.1.3

16 Jul 07:24
bd40727
Compare
Choose a tag to compare

#42 #43 Make sure the /tmp/log directory exists.

0.1.2

15 Jun 13:07
6156395
Compare
Choose a tag to compare
  • Fix Symfony 5.2 compatibility because Kernel::preBoot() broke the current implementation #37
  • Benefit from pre-warmed cache in console/worker context #41