0.2.21

#52, #53: Add the --stage option on more commands

0.2.20

#46 Fix the progress bar of bref deploy so that it displays correctly on Ubuntu

0.2.19

#43, #44: Add the intl extension by @t-geindre

The extension is not installed by default, it needs to be enabled in .bref.yml.

Read more about PHP extensions here.

0.2.18

• #34 Add New Relic extension
• #32 #36 Unused PHP extensions are removed from the lambda before uploading
• #30 #35 New bref deploy --stage=production option to deploy to a custom stage

0.2.17

#26 #29: Configure PHP flags and extensions using .bref.yml

For example:

php:
    configuration:
        max_execution_time: 300
    extensions:
        - redis

Here is the list of extensions available:

• Redis: redis
• MongoDB: mongodb

0.2.16

#27 Allow to choose the PHP version in .bref.yml, for example:

php:
    version: 7.2.6

Read more.

0.2.15

#24 & #25: New bref deploy --dry-run option
#22: New php bref.php bref:invoke command to replace bref local for local testing
#20: New bref invoke command to invoke the lambda
#21: New bref logs command to display the lambda's logs
#19: New bref remove command to delete the lambda

0.2.14

• #18 Speed up building lambdas when deploying or running them locally
• Fix #17: broken local command
• #16 Stream the output of bref deploy

0.2.13

#15 Bref internal files are auto-deployed:

Users do not have to add Bref internal files to serverless.yml anymore. You can remove the handler.js and '.bref/**' files from your include section in serverless.yml, however this is not mandatory.

0.2.12

#14: Opcache is now installed and configured

Opcache usually works in memory, compiling PHP code to opcode and caching it in memory between HTTP requests. Since on lambdas the PHP process is terminated between requests, the classic behavior of opcache doesn't work (the cache is cleared every time).

To make opcache work we enable its "file cache" mode where opcache writes the opcode into a file (with the opcache.file_cache option). When the PHP process starts, it reads the opcodes from the file cache.

On the API platform demo, when getting a list of books (uses the database):

• without opcache: 220ms
• with opcache: 105ms