book

Mastering Symfony

by Sohail Salehi

April 2016

Intermediate to advanced

290 pages

5h 51m

English

Packt Publishing

Read now

Unlock full access

eBooks, discount offers, and moreWhy subscribe?
What this book covers

Downloading the example codeDownloading the color images of this bookErrataPiracyQuestions
Why Symfony?Influenced by SymfonyHow bright is the future?
Installing Symfony via ComposerThe road mapChecking the installation
The big picture
Generating a new bundleBest practices
Controller/View interactionConditional templatesMake it dynamicDatabase configurationsGenerating an entityInstalling bundles created by others
Loading data fixtures
The importance of Continuous Integration
Creating a new instance
Installing ApacheInstalling MySQL and PHPInstalling JenkinsSetting up security and installing plugins in Jenkins
Configuring Jenkins
Sniff Symfony codes
How does GitHub alert Jenkins about new pushes?
Getting started with BDDIs BDD a replacement for TDD?
Installing and configuring BehatThe features we need for this projectMore information about the projectGherkin – the common language
Seeing it in actionHeadless versus zombieUsing the Selenium2 controller for automated tests
A scenario to show the user's detailsImplementing the user's details scenarioTesting the scenario
Installing the Codeception frameworkBootstrapping CodeceptionTest suitsThe testersAdding sample testsRunning the tests
Choosing between creating a Model or entity
Creating ERDs using MySQL WorkbenchAdding a new entityAdding a new relationshipCreating actual tables from a diagramGenerating entitiesData fixtures
Step one – creating a functional testDeveloping the missing codeStep two – creating the unit testsSetting up the database for a test environment in the right wayDropping and recreating the database for each testCreating unit testsWriting the code to pass the testRunning functional and unit testsStep three – creating an acceptance test
How security is organized in Symfony?AuthenticationAuthorization
Security settingsAdding the required configurations to FOSUserBundleAdding routesUpdating the tablesA simple road test
Introducing AliceBundleCreating data fixtures with AliceRelationship with AliceSetting up the login redirectionCreating tests for the new controllerCreating the Dashboard ControllerSecuring the dashboard
Installing and configuring Sonata bundleAdding contents to the dashboardCreating admin feature for entities with relations
Installing SonataUserBundleSonataUserBundle configurationUpdating the routesSetting the securityChecking the installationPutting SonataUserBundle in charge
Modifying the forms
How assets are organized
Bootstrap configuration
Rendering the menu in a template
Profile-related templates
The dashboard's contentsVisual blocks that provide statistics about tasksA feature file for the finished tasks blockImplementing the finished tasks blockImplementing the dashboard controller
Adding an attachment feature to the Task entity
The Team entity
Adding time tracking properties
Events, event dispatchers, and event listenersThe Notifier event listener
How to create a service
Creating and registering commands
The configuration partThe execution part
Console helpers
Why do we need different environments?The environment configuration file
The config fileThe front controller
Definition of a cacheCharacteristics of a good cache
Set expiration for dashboard pageValidation strategy
Doctrine cache

Content preview from Mastering Symfony

Custom bundles versus AppBundle

When we use AppBundle as a code base, the app/ directory of our project can be seen as part of AppBundle. Sure, it has other files and folders that take care of other bundles available in the /vendor directory, for example, but we can benefit a lot from the app/ folder.

For example, if you look at the MyBundle/Resources folder, you will find two subfolders named Resources/config/ and Resources/views/, which hold service definitions (and other required settings in the future) and template files for that bundle.

However, with AppBundle, we already have a folder named app/, so conveniently, we can use the available app/config for our configuration needs and app/Resources/views for our templates. Using this approach, ...