Updating the Symfony Demo application to Symfony 4
December 11, 2017 • Published by Javier Eguiluz
The Symfony Demo application is a reference application created to show how to develop Symfony applications following the recommended best practices. It's mainly used as a learning and teaching resource, so we keep it in sync with the latest Symfony versions and features.
During the past weeks we've worked hard to be ready for the Symfony 4 release and we've fully updated the application to Symfony 4 and Symfony Flex. The main changes introduced in the app are:
- Updated code to use as many PHP 7.1 features as possible;
- Used the flat and simple dir structure proposed by Symfony 4;
- Removed most of the service config thanks to the autowiring, _defaults, autoconfiguration and local binding;
- Created services for Doctrine repositories;
- Revamped the data fixtures to use modern DoctrineFixturesBundle practices;
- and all the other great simplifications allowed by Symfony 4!
Run this command to install the new Symfony Demo version:
1
$ composer create-project symfony/symfony-demo
A Community Effort
The Symfony Demo application is maintained by the Symfony community. We thank you all the developers who proposed ideas, reported issues, updated translations and contributed pull requests: Paweł Małolepszy, Piotr Grabski-Gradziński, Vladimir Chernyshev, Peter Kokot, David Maicher, Christophe Coevoet, Oleg Voronkovich, Victor Bocharsky and specially, Yonel Ceruto, for his tireless efforts to improve the app.
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
I was looking for specifics PR, as that would be great content to learn from.
Docs is good, but having real life example of what each bullet exactly meant for the projects would be awesome!
> Revamped the data fixtures to use modern DoctrineFixturesBundle practices;
I was specifically looking for that change. That particular commit wasn't made until after the 1.2.1 release. As a matter of fact, it was made just before 1.2.2 was tagged earlier today. So I assumed (bad practice, I'm sorry) that the latest release on GH (1.2.2 that was released today) was the release that this article was referring to (posted today).