// composer.json
{
"require": {
"php": ">=8.2",
"ext-ctype": "*",
"ext-iconv": "*",
"knplabs/knp-time-bundle": "^2.2", // v2.4.0
"php-cs-fixer/shim": "^3.46", // v3.46.0
"phpdocumentor/reflection-docblock": "^5.3", // 5.3.0
"phpstan/phpdoc-parser": "^1.25", // 1.25.0
"symfony/asset": "7.0.*", // v7.0.3
"symfony/asset-mapper": "7.0.*", // v7.0.2
"symfony/console": "7.0.*", // v7.0.2
"symfony/dotenv": "7.0.*", // v7.0.2
"symfony/flex": "^2", // v2.4.3
"symfony/framework-bundle": "7.0.*", // v7.0.2
"symfony/http-client": "7.0.*", // v7.0.2
"symfony/monolog-bundle": "^3.0", // v3.10.0
"symfony/property-access": "7.0.*", // v7.0.0
"symfony/property-info": "7.0.*", // v7.0.0
"symfony/runtime": "7.0.*", // v7.0.0
"symfony/serializer": "7.0.*", // v7.0.2
"symfony/stimulus-bundle": "^2.13", // v2.13.3
"symfony/twig-bundle": "7.0.*", // v7.0.0
"symfony/ux-turbo": "^2.13", // v2.13.2
"symfony/yaml": "7.0.*", // v7.0.0
"symfonycasts/tailwind-bundle": "^0.7.1", // v0.7.1
"twig/extra-bundle": "^2.12|^3.0", // v3.8.0
"twig/twig": "^2.12|^3.0" // v3.8.0
},
"require-dev": {
"symfony/debug-bundle": "7.0.*", // v7.0.0
"symfony/maker-bundle": "^1.52", // v1.53.0
"symfony/stopwatch": "7.0.*", // v7.0.0
"symfony/web-profiler-bundle": "7.0.*" // v7.0.2
}
}
4 Comments
where i can find the next mentioned tutorial about doctrine?
Hey @lulu
The Symfony 7 version of this tutorial is still in the planning stages but feel free to checkout our Symfony 6 Doctrine course in the meantime. The Doctrine packages are all super stable and even the release of ORM 3/DBAL 4 didn't bring major new features. Also, the integration with Symfony hasn't changed much between Symfony 6 and 7.
Victor, thank you for sharing your knowledge. Off to DBAL! Which was why I came here in the first place, to supplement a book I was reading before I got sidetracked by these amazing tutorials. Very professional. Your experience with this framework is very impressive.
Love the way these tutorials are set up where we can read along, or read the information before, during, and after watching the video. I took a few hours gleaning through this information, and feel more familiar with the file structure for it. I am sure I will need to return to this at the point where I ready to build my system that I will use to show potential employers my knowledge and to provide code examples. Not sure if I will go full on Symfony or build the system with components that include a lot of my own code.
Seems vanilla PHP, by the frameworks I have built using tutorials, might be hackable by changing the userID in form submissions. I need some serious confidence in the security of the system before I try to build a site for a customer that is for sure.
I just stopped by to say hello and to thank you.
Hey David,
First of all, thank you for your kind words about this tutorial! ❤️ Our whole team is happy to hear your feedback :)
Writing something from scratch may require much more time from you, so I would suggest reusing as many Symfony components as you need. And yeah, usually such OSS packages may have better security because they are constantly reviewed and fixed by many strong devs. Even if you will reuse some Symfony components in your custom code - this may not be as smooth as using the whole Symfony Framework from scratch, because that's what helps to integrate all those components into a single app easier.
So, even if writing something e.g. like a router system by your own may be fun and good for learning/undertanding, reusing already written components will definitely save you time and give you well written tested code so that you could focus on your actual app code.
And stay tuned! We are going to release more cool Symfony-related videos soon! :)
Cheers!
Cheers!
"Houston: no signs of life"
Start the conversation!