Chapters

23 Chapters | 2:22:24 |

01

Installing Doctrine

7:54
02

make:docker:database

5:24
03

docker-compose & Exposed Ports

4:46
04

docker-compose Env Vars & Symfony

4:59
05

doctrine:database:create & server_version

4:49
06

Entity Class

7:57
07

Migrations

5:34
08

Persisting to the Database

8:42
09

Fetching Data & The Repository

5:28
10

Entity objects in Twig

4:55
11

"5 Minutes Ago" Strings

3:15
12

Custom Repository Class

8:10
13

DQL & The Query Builder

6:49
14

Reusing Query Logic & Param Converters

3:35
15

Automatic Controller Queries: Param Converter

3:28
16

Smarter Entity Methods

7:57
17

Request Object & POST Data

8:08
18

Update Query & Rich vs Anemic Models

7:58
19

Data Fixtures

5:18
20

Foundry: Fixture Model Factories

5:56
21

Foundry Tricks

7:28
22

Sluggable: Doctrine Extensions

5:57
23

Timestampable & Failed Migrations

8:01

> Symfony 5 > Doctrine, Symfony & the Database

Buy Access to Course

20.

Foundry: Fixture Model Factories

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

28 Comments

Sort By

Login or Register to join the conversation

julien_bonnier 4 years ago edited

For those who would read this and didn't get a new make:factory command.

I think the new recipes (v1.10+) are not compatible with Symfony 5.1.x.

Make sure you register the bundle manually.

`# config/bundles.php

return [

// ...
Zenstruck\Foundry\ZenstruckFoundryBundle::class => ['dev' => true, 'test' => true],

];`

6 |

Victor SFCASTS julien_bonnier 4 years ago

Hey Julien,

Thanks for sharing this workaround, it might be helpful! Though, Symfony Flex should register the bundle automatically nevertheless any changes in the recipe. Might it be so that you disallowed the Symfony Flex plugin execution when you were installing the bundle? Anyway, makins sure the bundle is automatically register is a good idea 👍

Cheers!

1 |

Samuel E. Victor 4 years ago

Can you give more insight on how you would have disallowed the Symfony Flex Plugin? and making sure things are registering automatically? I also had to register the bundle manually for it to work.

|

Victor SFCASTS Samuel E. 4 years ago

Hey Samuel,

I would not suggest to disallow the bundle. To check - you can take a look at your composer.json file, in particular "config.allow-plugins" option. There should be "symfony/flex": true". If it's false, then the plugin is not allowed to run and so it won't ask you for installing new recipes and won't install them.

Also, please, make sure "allow-contrib" is set to "true" in "extra.symfony" option in case you're trying to install non-official recipe from symfony/recips-contrib repository.

If the config looks good in your composer.json - great, just try to reinstall the specific recipe with "symfony composer recipe:install" command. You may need to add --force and --reset flags if it does nothing without them.

I hope this helps.

Cheers!

1 |

Samuel E. Victor 4 years ago

Thanks for the insight! The "allow-contrib" was false for me. Also I didn't have an "allow-plugins" key/value pair under config either. So I am thinking by default these weren't added.

|

Victor SFCASTS Samuel E. 4 years ago

Hey Samuel,

If allow-contrib is false and you're installing a bundle from the symfony/recipe-contrib repo - that's the problem. You should make it true, and remove that key completely so Composer will ask you the next time. If no allow-plugins key - great, then it will be asked by Composer the next time too, just look closer at the output to do not miss replaying "yes" there.

After you change the config - you can try to remove the package with "composer remove" and then re-add it with "composer require" commands and this time it should ask, and if you replied yes - it would install the recipe. Or as I said, you can just force re-installing the recipe yourself with "recipe:install" command

Cheers!

1 |

Sean 5 years ago

Hello again. I swear Ill make it through one of these without running into an issue.

Tonight suddenly started getting an error running "composer require zenstruck/foundry --dev", which is weird because I installed it a few days ago.....I dunno.

If anyone else is getting `Your requirements could not be resolved to an installable set of of packages.` and it references doctrine/persistence what fixed it for me was editing my composer.json, under "require-dev" add the line "doctrine/persistence": "1.3.8", . Run "composer update", then try installing package again.

Edit: thought you could do markdown...I was wrong

3 |

Victor SFCASTS Sean 5 years ago

Hey Sean,

I just double-checked it: download the course code, goes to the start/ directory, require orm and zenstruck/foundry packs and it worked for me. So, not sure why exactly you hit that error, probably a new version was released that conflicted with your locked dependencies. Anyway, I'm glad you were able to get it working! And thank you for this tip - it might be useful to others.

Cheers!

|

Luca Victor 5 years ago

Hey Sean and Victor,

ran into the same issue. Updating composer.json helped me out as well.

|

Victor SFCASTS Luca 5 years ago

Hey Luca,

Great! What version of PHP do you have? Did you run the project from start/ directory or created a new project from scratch?

Cheers!

|

Luca Victor 5 years ago

I'm running PHP Version 7.3.11 and I created a new project from scratch.

|

Victor SFCASTS Luca 5 years ago

Hey Luca,

Thank you for sharing this info! We will try to investigate it.

Cheers!

|

kbond SFCASTS Victor 5 years ago

Hey all, this should be fixed in Foundry v1.1.2 (https://github.com/zenstruc... - I allow doctrine/persistence v2

|

Victor SFCASTS kbond 5 years ago

Hey Kevin,

Awesome! Thank you for the quick fix :)

Cheers!

|

weaverryan SFCASTS kbond 5 years ago edited

Thanks Kevin B.!

Yea, there is a "transition" happening right now due to some new Doctrine versions. About 2 weeks ago, DoctrineBundle started allowing doctrine/persistence 2, which means that new projects are now using that version. That means that if you try to install something that only allows v1, you get a dependency error... which is kind of hard to read in Composer. Btw, in Composer v2, the error message has been improved to help you understand this - https://github.com/composer...

Cheers!

|

Dang 4 years ago

Hello. In some previous tutorials, you presented us other library for the fixture called Alice Bundle. I wonder beacause this tuto is newer (Symfony 5) so this bundle zenstruck/foundry is better and I should use this instead for new project? Thanks

|

weaverryan SFCASTS Dang 4 years ago edited

Hey Dang!

Yes, mo Foundry is much better than Alice. Foundry didn't exist when I wrote the earlier tutorials that used Alice. I now *much* prefer Foundry of Alice :). So use it instead!

Cheers!

|

akshit 4 years ago

We were loading the data through entity manager before and it looked simple and easy. Then , what's the need for these App fixtures?

|

Victor SFCASTS akshit 4 years ago

Hey Brainiac,

Yes, Foundry definitely adds more overhead into your project than just simple fixtures, but it also provides more features out of the box. To know more about the features it brings - please, watch this screencast. Also, in the next video we cover some tricks, I'd also recommend you to watch. You can also find some explanation about Foundry on its GitHub repo page: https://github.com/zenstruc.... Or take a look at docs to see all benefits it can provide you if you require it in your project: https://symfony.com/bundles... .

But yeah, it's totally up you t use this or no, if you're happy with simple Doctrine fixtures and don't need all those Foundry features - great, just use them, it's totally valid :)

Cheers!

|

m3tal 4 years ago

Hi,

I would like to know, in big words, how I can create for example a test environment with separate docker. how I tell symfony to use other container for test environment.
thank you and have a nice day.

|

Victor SFCASTS m3tal 4 years ago

Hey Bogdan,

Unfortunately, we don't have any courses about Docker yet, but we will definitely want to release one in the future. For now, I can't tell you when it may happen, unfortunately. If you want a course about it - try to search on the internet, I bet there are a lot of examples you can reuse and modify for your needs. Also, I can recommend you to look at a few open PRs in Symfony Demo about adding Docker, I think you can stole some boilerplate code from there :)

- https://github.com/symfony/...
- https://github.com/symfony/...

I hope this helps!

Cheers!

1 |

Sherri 5 years ago edited

A few notes:

1) This way of calling createMany() is deprecated, I get a notice when calling doctrine:fixtures:load. The new way is like so:
QuestionFactory::createMany(20);
There is also a:
QuestionFactory::createOne();

2) The homepage twig template needs to be updated to show the proper votes count from the question object. The same as was done in the show template.

|

weaverryan SFCASTS Sherri 5 years ago edited

Hi Sherri!

Sorry for my very slow reply - but thanks for posting these!

> 1) This way of calling createMany() is deprecated

We'll get a note added about this so people are aware :) - thank you!

> 2) The homepage twig template needs to be updated to show the proper votes count from the question object. The same as was done in the show template.

You're right - I totally forgot about this piece.

Anyways, we always appreciate notes like these - we miss things, and sometimes things change - and we want to keep the tutorials as up-to-date as possible :).

Cheers!

|

Tim-K 5 years ago

Hey SymfonyCast-Team,

i have a Question of Concept:

I have already implemented classes in a folder called "Factory". I use these classes to help me in the regular use (env="prod") to create new objects and to store them in the database.

1) Is my understanding of "Factory" maybe wrong? (or how are such helper-functions called?)

2) Since I now want to use FOUNDRY, I run into trouble, because my "PersonFactory.php" already exists in the "Factory"-folder. But if I understand the concept of FOUNDRY correct these classes will never run on production (class extentions like 'ModelFactory' will not be available, as the package will not be installed on production ('composer require zenstruck/foundry *--dev*)) and so a merge of my current functions into the Foundry-Factories makes no sense.

Is it possible to change in the standard folder-name for FOUNDRY? (using the maker from the console)?

Or am I not working according convention with my current concept of FACTORY? If I need to change this it will be a big refactoring work...

Cheers
Tim

|

MolloKhan SFCASTS Tim-K 5 years ago edited

Hey Tim K.

> 1) Is my understanding of "Factory" maybe wrong? (or how are such helper-functions called?)
Usually a factory it's meant to create objects not persistin them in the database or any other storing mechanism

About your second question. Yes, Foundry will not be installed in your production server because it's a dev dependency, so you should not depend on it but in your tests or data fixtures. If you're having problems with classes using the same name, it can be easily fixed by using a different namespace for your classes.

Cheers!

|

Jonas ernesto P. 5 years ago

I have an error...
For me, Command "make:factory" is not defined.

|

sadikoff Jonas ernesto P. 5 years ago edited

Hey Jonas ernesto P.

I guess you have outdated MakerBundle! But wait, how did you get here? This course it not released yet! ;)

Cheers!

1 |

Jonas ernesto P. sadikoff 5 years ago

The videos are not yet, but the text is!
See you!

|

This tutorial also works great for Symfony 6!

Symfony 5 Doctrine 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.4.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/doctrine-bundle": "^2.1", // 2.1.1
        "doctrine/doctrine-migrations-bundle": "^3.0", // 3.0.2
        "doctrine/orm": "^2.7", // 2.8.2
        "knplabs/knp-markdown-bundle": "^1.8", // 1.9.0
        "knplabs/knp-time-bundle": "^1.11", // v1.16.0
        "sensio/framework-extra-bundle": "^6.0", // v6.2.1
        "sentry/sentry-symfony": "^4.0", // 4.0.3
        "stof/doctrine-extensions-bundle": "^1.4", // v1.5.0
        "symfony/asset": "5.1.*", // v5.1.2
        "symfony/console": "5.1.*", // v5.1.2
        "symfony/dotenv": "5.1.*", // v5.1.2
        "symfony/flex": "^1.3.1", // v1.21.6
        "symfony/framework-bundle": "5.1.*", // v5.1.2
        "symfony/monolog-bundle": "^3.0", // v3.5.0
        "symfony/stopwatch": "5.1.*", // v5.1.2
        "symfony/twig-bundle": "5.1.*", // v5.1.2
        "symfony/webpack-encore-bundle": "^1.7", // v1.8.0
        "symfony/yaml": "5.1.*", // v5.1.2
        "twig/extra-bundle": "^2.12|^3.0", // v3.0.4
        "twig/twig": "^2.12|^3.0" // v3.0.4
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.3", // 3.4.0
        "symfony/debug-bundle": "5.1.*", // v5.1.2
        "symfony/maker-bundle": "^1.15", // v1.23.0
        "symfony/var-dumper": "5.1.*", // v5.1.2
        "symfony/web-profiler-bundle": "5.1.*", // v5.1.2
        "zenstruck/foundry": "^1.1" // v1.5.0
    }
}

Previous Chapter

Next Chapter