Chapters

29 Chapters | 3:14:24 |

01

Flex, Versioning & extra.symfony.require

8:32
02

Managing Flex, extra.symfony.require & Version Constraints

5:02
03

Upgrading to Symfony 4.4

5:46
04

Selectively Committing Recipe Updates

4:35
05

Upgrading Recipes: New Commands!

6:36
06

Recipe Upgrade: symfony/console & bootstrap.php

8:24
07

Upgrading the FrameworkBundle Recipe (Part 1)

6:17
08

FrameworkBundle Recipe Part 2: The Kernel Class

8:37
09

Updating the TwigBundle Recipe

7:35
10

Updating the Mailer Recipe(s)

4:39
11

phpunit-bridge & routing Recipes

6:17
12

Updating security, translation & validator Recipes

5:08
13

Updating the webpack-encore-bundle Recipe

6:05
14

Fixing the First Deprecations

6:14
15

Upgrading KnpPaginatorBundle & PHP Platform Version

7:18
16

Upgrading/Migrating from StofDoctrineExtensions

4:50
17

Upgrading to DoctrineBundle 2.0

6:50
18

DoctrineBundle Updates & Recipe Upgrade

11:22
19

Fixing our Deprecations: Form, Controller & Mailer

7:34
20

Hunting the Final Deprecations

5:06
21

Upgrading to Symfony 5.0

9:10
22

Secrets Management Setup

9:35
23

Production Secrets

7:10
24

Overriding Secrets Locally (Local Vault)

4:04
25

Prod Vault Optimization & Vault for Tests

4:53
26

Validation Auto-Mapping

8:49
27

Migrate Password Hashing

9:46
28

PHP 7.4 preload

3:00
29

Is your Container Running? Catch It! lint:container

5:10

> Symfony 5 > Upgrading & What's New in Symfony 5!

Buy Access to Course

06.

Recipe Upgrade: symfony/console & bootstrap.php

Autoplay

Previous Chapter

Next Chapter

The first recipe I want to update is symfony/console. Let's get some more info about it:

composer recipes symfony/console

Just like before, it shows us some links: a link to what the recipe looked like at the moment we installed it - I'll paste that into my browser - and also a version of what the recipe looks like right now. Let's open up that one too.

Recipe Organization & History

We're not going to always study the history of a recipe like this, but I need to show you something. Because of the way that recipes are organized, if you want see what changed in a recipe since you installed it, it's not always as easy as looking at the history.

This is what the recipe looks like today. Click to look at the commit history. You might think:

Okay, I'll just go back and see what commits have been made to this recipe since my version.

That's a great idea, because sometimes knowing why something changed can be a huge help. But... the installed version of my recipe lives in a symfony/console/3.3/ directory. The new one lives in symfony/console/4.4/.

Let's look at this entire symfony/console directory. Oh, and make sure that you're looking at the master branch - the latest commits. Each recipe is allowed to have multiple versions. If you installed symfony/console version 3.3, Flex would install the 3.3 recipe. If you installed 4.2, you would get the 4.2 recipe. What if you installed symfony/console 4.1? You would get the 3.3 recipe. A new directory is created only when a recipe needs to be updated to show off a feature that's only available in a newer version.

So, it's kind of a strange versioning mechanism. When we installed this recipe, we installed the 3.3 version. Updating it would install the 4.4 version. So if you want to see the full history... it's tricky: you kind of need to look at the history of what commits have been made to the 4.4 branch... and also maybe the history of what's been done to the 4.2 branch.... and also maybe the commit history for the 3.3 branch.

But, it's not as bad as it sounds - I'm trying to deliver the bad news first. Most of the time, the reason a file was updated in a recipe will be pretty obvious. And when it's not, with a little digging, we can find the reason.

Let's update a Recipe

Okay, so how do we actually upgrade a recipe to the latest version? You can see the answer down here: composer recipes:install symfony/console --force -v.

But, it's not really a smart "update" system. That command tells Flex to completely re-install the symfony/console recipe using the latest version. Try it:

composer recipes:install symfony/console --force -v

Tip

Starting with symfony 5.1, the config/bootstrap.php is not used anymore. And so, you won't see it added when upgrading the recipe. You can safely delete this file: updates to your bin/console file now handle that file's job.

Nice! Thanks to the -v flag, it tells us what files it worked on. It says:

Created bin/console
Created config/bootstrap.php

Well, really, it modified those files... but at least in the version of Flex I'm using, it always says "created".

Let's see how things look. Run:

git status

Cool! 3 changed files. Just like with the MonologBundle recipe, we need to add these changes carefully: if we had any custom code in the files, the update process just replaced it. Run:

git add -p

The bin/console changes

The first file is bin/console... and it's a namespace change from Debug to ErrorHandler. This is updating our code to use a new ErrorHandler component - some features of the Debug component were moved there. So that's a good change.

It also... I don't know, added some if statement that prints a warning... it looks like it's just making sure we don't try to run this from inside a web server. Enter "y" to add both changes.

Investigating a Change

Next, woh! It removed a huge block of code from the bottom and tweaked an if statement further up. These changes are on config/bootstrap.php.

This... looks like some low-level, edge-case normalization of environment variables. So probably we want this. But let's pretend we don't know: we want to find out why this change was made.

How? By doing some digging! Go back to symfony/recipes/console. Start by looking in the 4.4/ directory - the version we're installing. Find config/bootstrap.php.

Wait... see the config/ directory? What does that little arrow mean? It means that this is actually a symbolic link to another directory: the 4.4/config directory is identical to 4.2/config.

Ok, let's go look there! Head into the 4.2/ directory, then config/. Woh! Another arrow! This time the bootstrap.php file is a symlink - pointing to, wow! A totally different recipe - a bootstrap.php file in framework-bundle.

The bootstrap.php file is the most complex file in the recipe system and it's shared across several recipes. Yep, I'm showing you the ugliest case.

Let's go find that: symfony/framework-bundle/4.2/config/bootstrap.php. Here is the file. To find the change, use the "blame" feature. Ok, the block of code we're looking at - lines 9 through 12 - have two different commits. Let's look at just one of them:

Allow correct environment to be loaded when .env.local.php exists

And we can even click to see the pull request: #647 if you want really dive into the details. In this case, the change fixes a bug if you use the .env.php.local file.

But, really, config/bootstrap.php is a low-level file that should almost always be identical in every project. So unless you're doing something super advanced, you will probably want to accept all of these changes.

This big removal of code? That was because in an earlier version of this recipe, your project may or may not have had this loadEnv() method on DotEnv: it was added in Symfony 4.2. If your app did not have that method, it added a bunch of code to "imitate" its behavior. We don't need that anymore. Thank you recipe update!

The last change is for the symfony.lock file. We don't even need to look at this: always accept these changes. This marks the recipe as updated and sometimes saves extra debugging info that might be useful later.

That may have seemed like a small step. But other than trying to figure out the reasons a file changed, this was a home run! We were able to update two low-level files, which will help make sure our app continues to work like we expect.

Go ahead and commit these changes. Then let's keep going. Next, we'll update the biggest and most important recipe: the one for symfony/framework-bundle.

19 Comments

Sort By

Kieran B. 2 years ago

is config/bootstrap.php no longer part of a recipe?

| Reply |

sadikoff SFCASTS Kieran B. 2 years ago edited

Hey Kieran B.

Yes it's so. It was dropped in Symfony 5.1 IIRC

Cheers!

| Reply |

Kieran B. sadikoff 2 years ago

Thanks Vladimir,

When updating recipes, does flex not remove files that are no longer used. Seems that the bootstrap file I had integrated with an older version of dotenv. The site worked file but when I installed phpunit then it would check to see if the bootstrap file was there and try to include it causing an issue. Removing the file manually worked but it did make me wonder what other cleanup I need to do.

| Reply |

sadikoff SFCASTS Kieran B. 2 years ago

Yeah that's a bummer! I also faced this issue when updated some projects. Honestly I don't know good approach to find such cases, I think the only way is to check recipes while updating stuff.

Cheers!

| Reply |

Polychronis 2 years ago edited

Trying to perform a "minor" version upgrade [ 5.2 to 5.3 ]
on a fresh/clean symfony 5.2 project
(i.e. `composer create-project symfony/website-skeleton:"5.2.*" s5test` )

Then i just add a home page for testing purposes (https://symfony.com/doc/current/page_creation.html)

In composer.json: i change:
"symfony/...": "5.2." to "symfony/...": "5.3."
"symfony/...": "^5.2 to "symfony/...": "^5.3"

[composer update "symfony/*" --with-all-dependencies] runs ok

To complete the upgrade i need to install 6 recipes

recipes: [symfony/routing, symfony/security-bundle, symfony/translation, symfony/twig-bundle] install ok...

But with these 2 recipes:

- symfony/console: 
after I install this one, when i run composer update:
i get: Executing script cache:clear [KO] [KO] Script cache:clear returned with error code 255 !! Script @auto-scripts was called via post-update-cmd
and php bin/console cache:clear does not do anything along with any other console cmd

- symfony/framework-bundle:
after I install this one i get an empty page on my browser
no debug toolbar and nothing at var/log/dev.log

To sum it up: after installing these 2 recipes:

console terminal does not work anymore
homepage does not display anything.

anyone had this issue ? any hints?

| Reply |

Polychronis Polychronis 2 years ago

installing runtime
`composer require symfony/runtime`
solves this issue...

for some reason at my setup the error did not hint a solution
while at an other setup it did.... found it at stackoverflow after posting a question there...

| Reply |

Victor SFCASTS Polychronis 2 years ago

Hey Polychronis,

Good catch on that "symfony/runtime". Unfortunately, it's difficult to say what may goes wrong without seeing the exact errors. For the future, I'd recommend you too check logs - they may hind with some problems. And yeah, another way to search on StackOverflow is also a good idea, well done :)

Cheers!

1 | Reply |

Trafficmanagertech 3 years ago

Doing this moved my .env.dist to .env and created the bootstrap.php + some additional .env.local and .env.test...
I really do not want to use .env files, I have for example 10 clients on the same machine, each of them has different db credentials, so the parameters should be different... The old good parameters.yaml, untracked from git, was perfect... is it possible to use symfony 5 without the dotenv component?

| Reply |

Ad F. Trafficmanagertech 3 years ago

You should also read this

| Reply |

Ad F. Trafficmanagertech 3 years ago

you should open an issue on github :)

| Reply |

Trafficmanagertech Trafficmanagertech 3 years ago

It seems I can't because the bin/console now has hardcoded references to dotenv... I'll leave it even if the variables inside the .env are not used anywhere

| Reply |

Victor SFCASTS Trafficmanagertech 3 years ago edited

Hey Trafficmanagertech ,

It still should be possible to use old-known parameters.yaml instead of env vars in Symfony. I'm not sure 100% if it works out of the box now (I think it should), but you may need to modify a few files in your project that link to the .env files. Also, for clarity, if you don't use env vars at all - I'd suggest to remove .env files completely from your project... or at least remove all env vars in those files. Unfortunately, if you use Symfony Flex - it will try to modify .env files on composer commands. If you want to continue using Symfony Flex - you would probably need to manually revert .env changes after each Composer installation.

About bin/console - you should be able to specify in what env you want to run the Symfony command with "--env" option, e.g:
"$ bin/console --env=prod"

Anyway, using parameters.yaml instead is still should be possible. Though, I'd recommend you to get used to .env files instead. Mostly, it's the same parameters but more flexible. I hope this helps!

Cheers!

1 | Reply |

Trafficmanagertech Victor 3 years ago

Hi, thank you very much,
yes we are already phasing out the parameters.yaml and moving all the settings to a `settings` table in the db, the only one setting that will remain will be the db connection string and you're right, it could be moved to the .env... (ultimately we want to move also that to the db, using a different db_name depending on the HTTP_HOST... we have a SaaS platform with up to 50 clients on one machine and it would be much easier)

| Reply |

Victor SFCASTS Trafficmanagertech 3 years ago edited

Hey Trafficmanagertech ,

Glad to hear you found a workaround! Yeah, it's up to you, but probably leaving as is using .env for DB connection is the simplest solution.

Cheers!

1 | Reply |

MolloKhan SFCASTS Trafficmanagertech 3 years ago edited

Hey Trafficmanagertech

That's a good question. If you don't want to manage your env vars in the Symfony way, you can totally do it. The first option would be to do what you did, just ignore the .env files and keep going. Or, you can modify the config/bootstrap.php to stop trying to use the DotEnv component and implement your own logic to initialize your env vars. Does it makes sense to you?

Cheers!

1 | Reply |

Nicholas Wright 4 years ago edited

I fell at the first hurdle with composer recipes symfony/console throwing:
[Symfony\Component\Console\Exception\CommandNotFoundException] Command "recipes" is not defined.

Running composer update fixed it.

| Reply |

Victor SFCASTS Nicholas Wright 4 years ago

Hey Nicholas,

Please, make sure you have the latest version of Composer. If not - try to upgrade to the latest. And if you still don't see the command - upgrade "symfony/flex" to the latest version as well. Let me know if after these steps you still don't have "recipes" command :)

Cheers!

| Reply |

didier2l 4 years ago edited

Hey Ryan !
there's a little error here :
composer recipes install symfony/console --force -v
It's missing the : between composer & recipes.

By the way, thanks for your amazing work on symfonycasts :)

| Reply |

Victor SFCASTS didier2l 4 years ago

Hey Didier2l,

Thank you for reporting it! I just merged PR that fixes it: https://github.com/knpunive... . So now it's fixed :)

Cheers!

| Reply |

Symfony 5

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.3.0",
        "ext-iconv": "*",
        "antishov/doctrine-extensions-bundle": "^1.4", // v1.4.2
        "aws/aws-sdk-php": "^3.87", // 3.110.11
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.10.1
        "doctrine/doctrine-bundle": "^2.0", // 2.0.6
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // 2.1.2
        "doctrine/orm": "^2.5.11", // v2.7.2
        "doctrine/persistence": "^1.3.7", // 1.3.8
        "easycorp/easy-log-handler": "^1.0", // v1.0.9
        "http-interop/http-factory-guzzle": "^1.0", // 1.0.0
        "knplabs/knp-markdown-bundle": "^1.7", // 1.8.1
        "knplabs/knp-paginator-bundle": "^5.0", // v5.0.0
        "knplabs/knp-snappy-bundle": "^1.6", // v1.7.0
        "knplabs/knp-time-bundle": "^1.8", // v1.11.0
        "league/flysystem-aws-s3-v3": "^1.0", // 1.0.23
        "league/flysystem-cached-adapter": "^1.0", // 1.0.9
        "league/html-to-markdown": "^4.8", // 4.8.2
        "liip/imagine-bundle": "^2.1", // 2.3.0
        "nexylan/slack-bundle": "^2.1", // v2.2.1
        "oneup/flysystem-bundle": "^3.0", // 3.3.0
        "php-http/guzzle6-adapter": "^2.0", // v2.0.1
        "phpdocumentor/reflection-docblock": "^3.0|^4.0", // 4.3.4
        "sensio/framework-extra-bundle": "^5.1", // v5.5.3
        "symfony/asset": "5.0.*", // v5.0.2
        "symfony/console": "5.0.*", // v5.0.2
        "symfony/dotenv": "5.0.*", // v5.0.2
        "symfony/flex": "^1.0", // v1.21.6
        "symfony/form": "5.0.*", // v5.0.2
        "symfony/framework-bundle": "5.0.*", // v5.0.2
        "symfony/mailer": "5.0.*", // v5.0.2
        "symfony/messenger": "5.0.*", // v5.0.2
        "symfony/monolog-bundle": "^3.5", // v3.5.0
        "symfony/property-access": "4.4.*|5.0.*", // v5.0.2
        "symfony/property-info": "4.4.*|5.0.*", // v5.0.2
        "symfony/security-bundle": "5.0.*", // v5.0.2
        "symfony/sendgrid-mailer": "5.0.*", // v5.0.2
        "symfony/serializer": "4.4.*|5.0.*", // v5.0.2
        "symfony/twig-bundle": "5.0.*", // v5.0.2
        "symfony/validator": "5.0.*", // v5.0.2
        "symfony/webpack-encore-bundle": "^1.4", // v1.7.2
        "symfony/yaml": "5.0.*", // v5.0.2
        "twig/cssinliner-extra": "^2.12", // v2.12.0
        "twig/extensions": "^1.5", // v1.5.4
        "twig/extra-bundle": "^2.12|^3.0", // v3.0.1
        "twig/inky-extra": "^2.12", // v2.12.0
        "twig/twig": "^2.12|^3.0" // v2.14.4
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.0", // 3.3.0
        "fzaninotto/faker": "^1.7", // v1.8.0
        "symfony/browser-kit": "5.0.*", // v5.0.2
        "symfony/debug-bundle": "5.0.*", // v5.0.2
        "symfony/maker-bundle": "^1.0", // v1.14.3
        "symfony/phpunit-bridge": "5.0.*", // v5.0.2
        "symfony/stopwatch": "4.4.*|5.0.*", // v5.0.2
        "symfony/var-dumper": "5.0.*", // v5.0.2
        "symfony/web-profiler-bundle": "4.4.*|5.0.*" // v5.0.2
    }
}

Previous Chapter

Next Chapter

Recipe Upgrade: symfony/console & bootstrap.php

Share this awesome video!

Recipe Organization & History

Let's update a Recipe

The bin/console changes

Investigating a Change

19 Comments

Delete comment?

What PHP libraries does this tutorial use?