Upgrading Existing Applications to Symfony Flex
Warning: You are browsing the documentation for Symfony 6.0, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
Upgrading Existing Applications to Symfony Flex
Using Symfony Flex is optional, even in Symfony 4, where Flex is used by default. However, Flex is so convenient and improves your productivity so much that it's strongly recommended to upgrade your existing applications to it.
Symfony Flex recommends that applications use the following directory structure, which is the same used by default in Symfony 4, but you can customize some directories:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
your-project/
├── assets/
├── bin/
│ └── console
├── config/
│ ├── bundles.php
│ ├── packages/
│ ├── routes.yaml
│ └── services.yaml
├── public/
│ └── index.php
├── src/
│ ├── ...
│ └── Kernel.php
├── templates/
├── tests/
├── translations/
├── var/
└── vendor/
This means that installing the symfony/flex
dependency in your application
is not enough. You must also upgrade the directory structure to the one shown
above. There's no automatic tool to make this upgrade, so you must follow these
manual steps:
Install Flex as a dependency of your project:
1
$ composer require symfony/flex
If the project's
composer.json
file containssymfony/symfony
dependency, it still depends on the Symfony Standard Edition, which is no longer available in Symfony 4. First, remove this dependency:1
$ composer remove symfony/symfony
Now add the
symfony/symfony
package to theconflict
section of the project'scomposer.json
file as shown in this example of the skeleton-project so that it will not be installed again:1 2 3 4 5 6 7 8
{ "require": { "symfony/flex": "^1.0", + }, + "conflict": { + "symfony/symfony": "*" } }
Now you must add in
composer.json
all the Symfony dependencies required by your project. A quick way to do that is to add all the components that were included in the previoussymfony/symfony
dependency and later you can remove anything you don't really need:1 2 3
$ composer require annotations asset orm-pack twig \ logger mailer form security translation validator $ composer require --dev dotenv maker-bundle orm-fixtures profiler
If the project's
composer.json
file doesn't contain thesymfony/symfony
dependency, it already defines its dependencies explicitly, as required by Flex. Reinstall all dependencies to force Flex to generate the configuration files inconfig/
, which is the most tedious part of the upgrade process:1 2
$ rm -rf vendor/* $ composer install
- Regardless of which of the previous steps you followed, at this point you'll have
lots of new config files in
config/
. They contain the default config defined by Symfony, so you must check your original files inapp/config/
and make the needed changes in the new files. Flex config doesn't use suffixes in config files, so the oldapp/config/config_dev.yml
goes toconfig/packages/dev/*.yaml
, etc. The most important config file is
app/config/services.yml
, which now is located atconfig/services.yaml
. Copy the contents of the default services.yaml file and then add your own service configuration. Later you can revisit this file because thanks to Symfony's autowiring feature you can remove most of the service configuration.Note
Make sure that your previous configuration files don't have
imports
declarations pointing to resources already loaded byKernel::configureContainer()
orKernel::configureRoutes()
methods.Move the rest of the
app/
contents as follows (and after that, remove theapp/
directory):app/Resources/views/
->templates/
app/Resources/translations/
->translations/
app/Resources/<BundleName>/views/
->templates/bundles/<BundleName>/
- rest of
app/Resources/
files ->src/Resources/
Move the original PHP source code files from
src/AppBundle/*
, except bundle specific files (likeAppBundle.php
andDependencyInjection/
), tosrc/
and update the namespace of each moved file to beApp\...
(advanced IDEs can do this automatically).In addition to moving the files, update the
autoload
andautoload-dev
values of thecomposer.json
file as shown in this example to useApp\
andApp\Tests\
as the application namespaces.If you used multiple bundles to organize your code, you must reorganize your code into
src/
. For example, if you hadsrc/UserBundle/Controller/DefaultController.php
andsrc/ProductBundle/Controller/DefaultController.php
, you could move them tosrc/Controller/UserController.php
andsrc/Controller/ProductController.php
.- Move the public assets, such as images or compiled CSS/JS files, from
src/AppBundle/Resources/public/
topublic/
(e.g.public/images/
). - Remove
src/AppBundle/
. - Move the source of the assets (e.g. the SCSS files) to
assets/
and use Webpack Encore to manage and compile them. SYMFONY_DEBUG
andSYMFONY_ENV
environment variables were replaced byAPP_DEBUG
andAPP_ENV
. Copy their values to the new vars and then remove the former ones.- Create the new
public/index.php
front controller copying Symfony's index.php source and, if you made any customization in yourweb/app.php
andweb/app_dev.php
files, copy those changes into the new file. You can now remove the oldweb/
dir. - Update the
bin/console
script copying Symfony's bin/console source and changing anything according to your original console script. - Remove the
bin/symfony_requirements
script and if you need a replacement for it, use the new Symfony Requirements Checker. - Update the
.gitignore
file to replace the existingvar/logs/
entry byvar/log/
, which is the new name for the log directory.
Customizing Flex Paths
The Flex recipes make a few assumptions about your project's directory structure.
Some of these assumptions can be customized by adding a key under the extra
section of your composer.json
file. For example, to tell Flex to copy any
PHP classes into src/App
instead of src
:
1 2 3 4 5 6 7
{
"...": "...",
"extra": {
"src-dir": "src/App"
}
}
The configurable paths are:
bin-dir
: defaults tobin/
config-dir
: defaults toconfig/
src-dir
defaults tosrc/
var-dir
defaults tovar/
public-dir
defaults topublic/
If you customize these paths, some files copied from a recipe still may contain references to the original path. In other words: you may need to update some things manually after a recipe is installed.