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

Why do we need different environments?


An environment basically provides running instructions for the same code base. It does not change anything in the code itself. It simply tells Symfony when the code is running, which tools and components should accompany it, and what set of parameters should be used.

The default Symfony environments are Dev, Test, and Prod. As their names suggest, they utilize Symfony tools for our code to run in development, test, and production environments respectively.

So what do they mean and how are they different from each other? For example, when we are developing and testing a web application, we need to get as much debug information as possible to hunt down a thrown exception. Running Symfony's Profiler, Logger, and other tools slows down the overall application performance, but in return provides valuable information that helps us spot and fix the problem.

On the other hand, when the application is fully developed and tested, all we need to do is maximize the...