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

Chapter 6. Dashboard and Security

It is nice to have entities and business logic in place. What would be nicer is having a control panel where we can Create,Read,Update, and Delete (CRUD) them and make sure that only specific users with the right privileges can have access to it. This sounds like a firewalled and secured area of the project.

In this chapter, we will see how to set up security and firewalls in Symfony, and then create a user management system using FOSUserBundle. After knowing the basics, we step into one of the biggest Symfony projects, Sonata, and use some of its bundles. We will see how to use SonataAdminBundle to manage entities from the backend. However, as an account owner (not administrator), we need to be able to manage our workspaces, projects, tasks, and members from the frontend as well. This means that we need to set up at least two firewalls for this project. One will be built in the frontend where every member keeps his own stuff, and one will be set for the...