Chapters

23 Chapters | 2:20:28 |

01

Bundles!

6:11
02

KnpMarkdownBundle & Service

7:55
03

Cache Service

5:01
04

Configuring Bundles

6:30
05

The Service Container & Autowiring

6:23
06

Configuring the Cache Service

6:45
07

Environments

9:08
08

Controlling the prod Environment

4:26
09

Creating a Service

5:03
10

Autowiring Dependencies into a Service

6:45
11

Parameters

7:59
12

Service Config & Non-Autowireable Arguments

7:02
13

All about services.yaml

6:21
14

Binding Global Arguments

3:01
15

Named Autowiring

5:18
16

Fetching Non-Autowireable Services

5:58
17

Controllers: Boring, Beautiful Services

2:55
18

Environment Variables

8:29
19

The Secrets Vault

7:39
20

Using & Overriding Secrets

5:21
21

MakerBundle & Autoconfigure

4:42
22

Playing with a Custom Console Command

4:44
23

Making a Twig Extension (Filter)

6:51

> Symfony 5 > Symfony 5 Fundamentals: Services, Config & Environments

Buy Access to Course

04.

Configuring Bundles

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

20 Comments

Sort By

Login or Register to join the conversation

Favian P. 6 years ago edited

I followed every single step and when I was die dumping the markdown object the parser was still set to max, I figured out it was a cache problem, so if you find yourself in the same spot with me run:
./bin/console cache:clear
and it should work

9 |

zahariastefan462 Favian P. 4 years ago

Thank you very much for sharing with us! I had exactly this problem.

|

Victor SFCASTS zahariastefan462 4 years ago

Hey Pill,

Thank you for confirming this solution helped you!

Cheers!

1 |

Oblong of Orange Favian P. 4 years ago

Took a little while for this tip to work for me, I cleared the cache, and after it completed refreshed the page a number of times, but it still returned markdown.parser.max each time. When I calmed down and did nothing for moment (around 30 seconds or so) and then refreshed, it was using markdown.parser.light as expected. Thank you!

|

Jewel F. Favian P. 5 years ago

Thanks for tip

|

Victor SFCASTS Favian P. 6 years ago

Hey Poputa,

Thanks for this tip! First of all, it depends in which Symfony env you're... in prod you have to clear the cache first to see any changes, but in dev it should not be necessary. Yeah, sometimes you have to do it in dev, especially when you use a virtual machine or Docker, I just noticed this a few times. So, in any weird situation it's always a good idea to try to clear the cache first. If it does not help - then look into it deeper.

Cheers!

|

Niclas H. 4 years ago edited

Just incase anybody is as retarded as I am:
Running ./bin/console config:dump KnpMarkdownBundle only dumps the <b>default</b> configuration for that service.
In the video, they validated that the config was updated to use markdown.parser.light by adding dd($markdownParser) and checking the browser to see which class is being used.

Edit: As Diego points out below, the two commands are:

symfony console debug:config KnpMarkdownBundle (your current config)
symfony console config:dump KnpMarkdownBundle (the default config)

1 |

MolloKhan SFCASTS Niclas H. 4 years ago edited

Hey Niclas H.

Lol - thank's for sharing it, you can also run bin/console dump:config to check your current configuration

Cheers!

|

Ruslan I. 4 years ago

Why was this autowiring system invented?
We could just write use statement on top of the file and then inside of a method just instantiate manually an object we want and configure it how we want via arguments instead of config files?
I'm just wondering, because at first I didn't like this system, but I get used to it

|

Victor SFCASTS Ruslan I. 4 years ago

Hey Phy!

Well, first of all, in Symfony services are created by Dependency Injection Container (DIC) that knows how to create them. And it create them only on request. I.e. if during the request the service was never been called from the container - it also was never created. Yes, you can instantiate services manually in your code, it would mean you need to pass all the required arguments there, including injection other services or passing some parameters... but why do it manually when DIC may do it for you? All you need to do - teach DIC how to create the service, and then in the code just call that service, that's it. Also, DIC controls that only one instance of the service is created during the request. It means that if you call the same service in a few separate spots of your code - you will get the exact same instance of the service in all those spots. Manually, it would be difficult for you to do this if you instantiate it manually, because sometimes it's difficult to pass the created instance to all the spots correctly without violation code quality.

I hope it clarify things for you now!

Cheers!

1 |

Covi A. 4 years ago edited

I am trying to create new bundle in symfony 5.3*. but i can't did it. because when i try to create a new bundle first of all i need generate:bundle command. but i could not find it inside bin/console.
bin/console generate:bundle command gave me this error
`There are no commands defined in the "generate" namespace.

You may be looking for a command provided by the "SensioGeneratorBundle" which is currently not installed. Try running "composer require sensio/generator-bundle `
".
then i try to install composer require sensio/generator-bundle. after this command it's gave me this error

`mono@mono:~/Projects/apptest$ composer require sensio/generator-bundle
Using version ^3.1 for sensio/generator-bundle
./composer.json has been updated
Running composer update sensio/generator-bundle
Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "5.3.*"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

Problem 1

- sensio/generator-bundle[3.1.0, ..., v3.1.7] require symfony/framework-bundle ~2.7|~3.0 -> found symfony/framework-bundle[v2.7.0, ..., v2.8.52, v3.0.0, ..., v3.4.47] but it conflicts with your root composer.json require (5.3.*).
- Root composer.json requires sensio/generator-bundle ^3.1 -> satisfiable by sensio/generator-bundle[3.1.0, ..., v3.1.7].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
`

so i can't find any right way to generate a new bundle. could you please give me any suggestion what can i do for create a new bundle in symfony 5.3* version. and also please tell me what wrong i am doing.
thank you

|

Victor SFCASTS Covi A. 4 years ago

Hey Monoranjan,

Yes, unfortunately, there's no a command that would generate a bundle for you, today you're trying to create the bundle yourself. Just literally open any bundle you're using and steal some boilerplate code. The bundle's structure you can find here: https://symfony.com/doc/cur...

That sensio/generator-bundle is abandoned and does not maintain anymore, which means you can't use it for Symfony 4 / 5. Since Symfony 4 we get rid of splitting your project code into bundles, so only third-party bundles are left that are supposed to be reusable in more than one project and should be installed via Composer in vendor/ dir. So, in theory you need to create a new bundle very rare, that's why there's no generate command so far, and yes, it's kinda requires some experience to work with the bundles if you want to create a new one.

So, following our tutorial about creating reusable bundles: https://symfonycasts.com/sc... and the docs I linked above you should be able to create a bundle I think. If you get stuck somewhere on that tutorial - let us know in the comments below the video and we will try to help you.

I hope this helps!

Cheers!

|

RobinBastiaan 5 years ago edited

What is the difference between ./bin/console config:dump [name] and ./bin/console config:dump-reference [name]? In the documents I see this alternative command popping up.

Edit: I just tested this command in my project, and it seems it is just an alias for the same thing.

|

Victor SFCASTS RobinBastiaan 5 years ago

Hey Robin,

Those are the exact same command :) Symfony console has a really cool feature when you can make sorter command names, so the original command name is "config:dump-reference", but you can make it shorter and type only "config:dump-ref", or even shorter like "config:dump", or go crazy and type: "conf:dump", or even "c:d" :)

So, literally, to call that "config:dump-reference" - you can just type "bin/console c:d" and if Symfony won't find more than one command that matches your short name - it will call it. But sometimes Symfony may find more than one command and then it will fail asking you to be more specific.

To be sure about the full command name that is called when you call a short version of it - you can add "--help" option, e.g. "bin/console config:dump --help" will show you that behind the scene it calls "config:dump-reference" command.

I hope this helps ;)

Cheers!

2 |

Jewel F. 5 years ago

I have added the knp_markdown.yaml file within the config->packages directory and added the "service: markdown.parser.light" by following you. But It do nothing, even I do mistakes on "services" instead of "service".

|

Victor SFCASTS Jewel F. 5 years ago

Hey Md,

I see that clearing the cache helped you. I just curious if you use any virtualization tool like Docker, etc. Probably you loaded the website in prod mode instead? Are you sure you were in dev mode? Only in dev mode Symfony rebuilds the cache on every page reload, for prod you need to clear the cache to see changes.

Cheers!

|

Jewel F. Victor 5 years ago edited

Thanks victor for repying me.
I was on prod mode, and I also use Docker.

|

Victor SFCASTS Jewel F. 5 years ago

Hey Md,

Yeah, then you have to clear the cache manually in prod to see changes. If you use Docker - even in dev mode it's always a good idea to clear the cache first to see if this helps, as filesystem is shared between your host machine and containers.

Cheers!

|

Jewel F. Jewel F. 5 years ago edited

Problem solved by following Jewel F.

|

Victor SFCASTS Jewel F. 5 years ago

Hey Md,

Thanks for confirming this helped you! https://symfonycasts.com/sc...

Cheers!

|

This tutorial also works great for Symfony 6!

Symfony 5

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.3.0 || ^8.0.0",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "knplabs/knp-markdown-bundle": "^1.8", // 1.9.0
        "sensio/framework-extra-bundle": "^6.0", // v6.2.1
        "sentry/sentry-symfony": "^4.0", // 4.0.3
        "symfony/asset": "5.0.*", // v5.0.11
        "symfony/console": "5.0.*", // v5.0.11
        "symfony/debug-bundle": "5.0.*", // v5.0.11
        "symfony/dotenv": "5.0.*", // v5.0.11
        "symfony/flex": "^1.3.1", // v1.21.6
        "symfony/framework-bundle": "5.0.*", // v5.0.11
        "symfony/monolog-bundle": "^3.0", // v3.6.0
        "symfony/profiler-pack": "*", // v1.0.5
        "symfony/routing": "5.1.*", // v5.1.11
        "symfony/twig-pack": "^1.0", // v1.0.1
        "symfony/var-dumper": "5.0.*", // v5.0.11
        "symfony/webpack-encore-bundle": "^1.7", // v1.8.0
        "symfony/yaml": "5.0.*" // v5.0.11
    },
    "require-dev": {
        "symfony/maker-bundle": "^1.15", // v1.23.0
        "symfony/profiler-pack": "^1.0" // v1.0.5
    }
}

Previous Chapter

Next Chapter