Chapters

25 Chapters | 2:34:05 |

01

Bundles!

4:31
02

New Bundle, New Service: KnpTimeBundle

5:09
03

Finding & Using the Services from a Bundle

6:38
04

The HTTP Client Service

6:23
05

The Cache Service

8:05
06

Bundle Config (to Control Bundle Services)

6:03
07

Configuring the Cache Service

5:39
08

debug:container & How Autowiring Works

7:41
09

Environments

8:55
10

The "prod" Environment

6:06
11

Creating a Service

5:55
12

Dependency Injection

9:34
13

Parameters

6:45
14

Manual Service Config in services.yaml

4:24
15

All About services.yaml

10:27
16

Bind Arguments Globally

3:40
17

Named Autowiring & Scoped HTTP Clients

4:43
18

Non-Autowireable Services

6:41
19

Controllers are Services Too!

2:49
20

Environment Variables

7:53
21

The Secrets Vault

5:46
22

Reading Secrets vs Env Vars

6:53
23

MakerBundle & Autoconfiguration

4:27
24

Customizing a Command

4:20
25

Command: Autowiring & Interactive Questions

4:38

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

Buy Access to Course

06.

Bundle Config (to Control Bundle Services)

|

|

Autoplay

Previous Chapter

Next Challenge

Login or register to check out the script

2 Comments

Sort By

Login or Register to join the conversation

BYT 3 years ago edited

I want to keep the controller, templates, forms, css and js all in one folder to organize them together in one folder because they are easy to find. When there are thousands of them and spread out across different folder then it's not easy to find them all work on. How can I have that setup? The common templates could stay in the default templates folder.

|

Victor SFCASTS BYT 3 years ago

Hey BYT,

That will be difficult to achieve because as templates everything in Symfony should be in its specific directory. Form types in src/, CSS and JS files - in assets/, Twig templates - in the templates/ dir, etc. So, I would recommend you to keep everything in its own place.. but use a specific naming. For example, if you have a form named RegistrationForm.php - you can related files in next folders:

src/Form/RegistrationForm.php
templates/form/registration.html.twig
assets/form/registration.js
assets/form/registration.css

So as you can see, every file named "registration" and I suppose you will be able to find related files very easily. Or, alternatively, you can name folders instead of files, something like:

assets/registration/form.js
assets/registration/form.css
etc.

I hope this helps!

Cheers!

1 |

Symfony 6.1

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "knplabs/knp-time-bundle": "^1.18", // v1.19.0
        "symfony/asset": "6.1.*", // v6.1.0-RC1
        "symfony/console": "6.1.*", // v6.1.0-RC1
        "symfony/dotenv": "6.1.*", // v6.1.0-RC1
        "symfony/flex": "^2", // v2.4.5
        "symfony/framework-bundle": "6.1.*", // v6.1.0-RC1
        "symfony/http-client": "6.1.*", // v6.1.0-RC1
        "symfony/monolog-bundle": "^3.0", // v3.8.0
        "symfony/runtime": "6.4.3", // v6.4.3
        "symfony/twig-bundle": "6.1.*", // v6.1.0-RC1
        "symfony/ux-turbo": "^2.0", // v2.1.1
        "symfony/webpack-encore-bundle": "^1.13", // v1.14.1
        "symfony/yaml": "6.1.*", // v6.1.0-RC1
        "twig/extra-bundle": "^2.12|^3.0", // v3.4.0
        "twig/twig": "^2.12|^3.0" // v3.4.0
    },
    "require-dev": {
        "symfony/debug-bundle": "6.1.*", // v6.1.0-RC1
        "symfony/maker-bundle": "^1.41", // v1.42.0
        "symfony/stopwatch": "6.1.*", // v6.1.0-RC1
        "symfony/web-profiler-bundle": "6.1.*" // v6.1.0-RC1
    }
}

Previous Chapter

Next Challenge