Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

Generating CRUD


Without getting into much trouble, generate CRUD for all four entities so far. This will be the basic structure of what we need. We will build the rest of our controllers on top of it. I will show you the settings for Workspace and you can do the same for the rest of entities (or get the finished codes from the 0.1.6 tag in the GitHub repository):

$ bin/console doctrine:generate:crud
The Entity shortcut name: AppBundle:Workspace
Do you want to generate the "write" actions [no]? yes
Configuration format (yml,xml,php or annotation) [annotation]: yml
Routes prefix [/workspace]:
Confirm automatic update of the Routing [yes]? 
Importing the CRUD routes: OK

As you can see, I chose yml for the configuration file to keep everything consistent.

This command added a new resource to the bundle's routing.yml file:

# src/Mava/CoreBundle/Resources/config/routing.yml
#...
core_workspace:
    resource: "@AppBundle/Resources/config/routing/workspace.yml"
    prefix:   /workspace
#...

This resource...